292307 - When setting an IPv6 link-local address for a HTTP proxy address, the address scope information is set on the wire.

Status: RESOLVED DUPLICATE of bug 464162

(Core :: Networking, defect)

Description

[qing.li]

User-Agent:       Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1; .NET CLR 1.1.4322)
Build Identifier: Mozilla/5.0 (Windows, U; Windows NT 5.1; en-US; rv:1.7.6) Gecko/20050317 Firefox/1.0.2

The browser put the following on the wire.
   "GET http://[fe80::2b0:d0ff:fe25:689%4]/readme.txt HTTP/1.1
    HOST: [fe80::2b0:d0ff:fe25:689%4]"
The address scope information "%4" as in interface #4 should never be sent.

Reproducible: Always

Steps to Reproduce:
1.Set the HTTP proxy address to an IPv6 link-local address
2.Issue the GET command

Actual Results:  
HTTP/1.1 400 Bad Request is returned


Expected Results:  
  "GET http://[fe80::2b0:d0ff:fe25:689]/readme.txt HTTP/1.1
    HOST: fe80::2b0:d0ff:fe25:689"

Comment 1

[Darin Fisher]

Hmm... is there an RFC somewhere that explains how to deal with this?  Should
the browser simply discard that information (i.e., the trailing"%4")?

Comment 2

[Gervase Markham [:gerv]]

This is an automated message, with ID "auto-resolve01".

This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.

While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.

If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.

The latest beta releases can be obtained from:
Firefox:     http://www.mozilla.org/projects/firefox/
Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html
Seamonkey:   http://www.mozilla.org/projects/seamonkey/

Comment 3

[Gervase Markham [:gerv]]

This bug has been automatically resolved after a period of inactivity (see above
comment). If anyone thinks this is incorrect, they should feel free to reopen it.

Comment 4

[David A. Madore]

Reopening this bug because I just encountered it with Firefox/3.0b4pre.

In response to comment #1 my interpretation of RFC 2732 is that there should be no scope identifier there.  In any case it wouldn't even make sense to put one because the interface identifier makes sense only for the client's computer/kernel/network stack, the server can't possibly do anything useful with it.

Comment 5

[Christian :Biesinger (don't email me, ping me on IRC)]

duping forward because that bug has a patch :/