Wireshark-bugs: [Wireshark-bugs] [Bug 8535] Url parse bug
Date Index · Thread Index · Other Months · All Mailing Lists
Date Prev · Date Next · Thread Prev · Thread Next
From: bugzilla-daemon@xxxxxxxxxxxxx
Date: Fri, 29 Mar 2013 04:51:09 +0000

Comment # 2 on bug 8535 from 
A little more detail:

    GET /http://qqshow2-item.qq.com/1000000/11900/02/ HTTP/1.1

is a Request-Line:

    http://tools.ietf.org/html/rfc2616#section-5.1

and

    /http://qqshow2-item.qq.com/1000000/11900/02/

is the Request-URI in the Request-Line:

    http://tools.ietf.org/html/rfc2616#section-5.1.2

According to RFC 2396:

    http://tools.ietf.org/html/rfc2396

an absoluteURI is:

    absoluteURI   = scheme ":" ( hier_part | opaque_part )

so

    /http://qqshow2-item.qq.com/1000000/11900/02/

is *NOT* a valid absoluteURI - the leading / is wrong.

    http://qqshow2-item.qq.com/1000000/11900/02/

*would* be a valid absoluteURI - and, if the request were

    GET http://qqshow2-item.qq.com/1000000/11900/02/ HTTP/1.1

*then* Wireshark should show http://qqshow2-item.qq.com/1000000/11900/02/ as
the full request URI.

However, the leading / means it's an abs_path, not an absoluteURI, so the
"http:" is just part of the abs_path, not a scheme, and the correct full URL
would be

    http://qqshow2-item.qq.com/http://qqshow2-item.qq.com/1000000/11900/02/

You are receiving this mail because:
  • You are watching all bug changes.