447748 - SOCKS Proxy is non-compliant: if you try to give a server response with a dns name the client only munches the 4 bytes for ip, even if marked.

Status: NEW

(Core :: Networking: Proxy, defect, P5)

Description

[Bill Ferguson]

User-Agent:       Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US; rv:1.9.0.1) Gecko/2008070206 Firefox/3.0.1
Build Identifier: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US; rv:1.9.0.1) Gecko/2008070206 Firefox/3.0.1

Socks5 servers can respond with the bind ip via either an ip address or dns name. firefox 3.0+ does not respond correctly to the dns name, and assumes an ip address only.

Was writing a server to spec and noticed this.

Reproducible: Always

Steps to Reproduce:
1. Set socks proxy to one that returns hostnames for server responses
2. ????
3. No profit (like 4+ bytes in the return stream that don't belong)
Actual Results:  
3. No profit (like 4+ bytes in the return stream that don't belong)

Expected Results:  
Loads properly.
Check field for dns name in server reply, and munch the bytes as needed.

Easy to fix, will take a look at moz src tomorrow, probably not noticed by many people, but must **** off those who do. Don't know how many servers do this actually, probably not many.

Comment 1

[benc]

Got any vendor info?

Comment 2

[Firefox Bug Husbandry Bot]

Bulk change to priority: https://bugzilla.mozilla.org/show_bug.cgi?id=1399258

Comment 3

[Firefox Bug Husbandry Bot]

Bulk change to priority: https://bugzilla.mozilla.org/show_bug.cgi?id=1399258

Comment 4

[Jens Stutte [:jstutte]]

Bulk-downgrade of unassigned, >=3 years untouched DOM/Storage bug's priority.

If you have reason to believe this is wrong, please write a comment and ni :jstutte.

Comment 5

[BMO Automation]

Moving bug to Core/Networking: Proxy.