incorrect address format after CONNECT when using numeric IPv6 address and SSL through proxy

RESOLVED FIXED in mozilla1.9.3a2

Status

()

Core
Networking: HTTP
RESOLVED FIXED
10 years ago
8 years ago

People

(Reporter: visibilis, Assigned: Biesinger)

Tracking

unspecified
mozilla1.9.3a2
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(URL)

Attachments

(1 attachment)

(Reporter)

Description

10 years ago
User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9) Gecko/2008052906 Firefox/3.0
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9) Gecko/2008052906 Firefox/3.0

When connecting to e.g. https://[fd00::1]:1000 using a proxy, I see the following with tcpdump:
CONNECT fd00::1:1000
Squid will reply, that it cannot retrieve the URL: fd00:443.
IE sends this:
CONNECT [fd00::1]:1000
and it succeeds.


Reproducible: Always

Steps to Reproduce:
1. Set a proxy for https
2. Try to connect to a site using numeric IPv6 address and SSL
Actual Results:  
The proxy replies with an error.
Component: General → Networking
Product: Firefox → Core
QA Contact: general → networking
Assignee: nobody → cbiesinger
Status: UNCONFIRMED → NEW
Component: Networking → Networking: HTTP
Ever confirmed: true
QA Contact: networking → networking.http
Created attachment 426696 [details] [diff] [review]
patch
Attachment #426696 - Flags: review?(bzbarsky)
Attachment #426696 - Flags: review?(bzbarsky) → review+
Question:

    // scope id is not needed for Host header.                                
    int scopeIdPos = host.FindChar('%');   

I thought '%' was used for zones in IPv6. 

http://en.wikipedia.org/wiki/IPv6_address#Link-local_addresses_and_zone_indices
Yes, but the scope ID is only meaningful on the client. The client's scope ID is meaningless on the server.
http://hg.mozilla.org/mozilla-central/rev/5a153fc2dc6f
Status: NEW → RESOLVED
Last Resolved: 8 years ago
OS: Windows XP → All
Hardware: x86 → All
Resolution: --- → FIXED
Target Milestone: --- → mozilla1.9.3a2
(plus http://hg.mozilla.org/mozilla-central/rev/8713065f5705)
You need to log in before you can comment on or make changes to this bug.