HTTP doesn't remember IPv6 scope for further redirections

UNCONFIRMED
Unassigned

Status

()

Core
Networking: HTTP
P3
normal
UNCONFIRMED
8 years ago
9 months ago

People

(Reporter: Mathias Gaunard, Unassigned)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: [necko-backlog])

(Reporter)

Description

8 years ago
User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-GB; rv:1.9.1.9) Gecko/20100401 Ubuntu/9.10 (karmic) Firefox/3.5.9
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-GB; rv:1.9.1.9) Gecko/20100401 Ubuntu/9.10 (karmic) Firefox/3.5.9

Accessing a website using a link-local IPv6 address and a scope id, such as
http://[fe80::20d:7cff:fe00:37fe%eth0]/
works fine, and with the fix to bug #464162 the Host header that is sent is
[fe80::20d:7cff:fe00:37fe].

As a result, when the server wants to do a redirection to another page, it sends a Location header like this:
http://[fe80::20d:7cff:fe00:37fe]/path/to/something

Which the browser fails to follow, since it is lacking which interface to use.
The fix would be to remember the scope and reuse it for any further link or redirection emitted from that connection.

Reproducible: Always

Steps to Reproduce:
1. Configure two network interfaces with link-local IPv6 support
2. Configure a HTTP server with a link-local address reachable from the first interface
3. Setup the HTTP server so that accessing the root causes a redirection to another path
4. Connect to http://[<link-local IPv6 address>%<first network interface name>]/
Actual Results:  
The redirection doesn't happen.

Expected Results:  
The browser gets redirected properly.
should do only if chrome also does (which I suspect doesn't)
Whiteboard: [necko-backlog]
You need to log in before you can comment on or make changes to this bug.