37366 - access through a squid proxy fails for ftp

Status: VERIFIED WORKSFORME

(Core :: Networking, defect, P3)

Description

[Ruairi Hickey]

If I try access ftp sites when my ftp proxy is set I recieve a blank document.
I assume this is due to squid returning http pages to an ftp request.  This
affects at least Windows and Linux (IE5 and lynx work correctly)

Comment 1

[Gervase Markham [:gerv]]

-> Networking.

Gerv

Comment 2

[Asa Dotzler [:asa]]

reassign

Comment 3

[Gervase Markham [:gerv]]

[e-mail] - It could be that Squid doesn't work with HTTP 1.1. Set:
user_pref("network.http.proxy.keep-alive", false);
in prefs.js to turn off HTTP 1.1.

Does that improve matters?

Gerv

Comment 4

[Asa Dotzler [:asa]]

setting status to New

Comment 5

[Gagan]

Gerv: that is incorrect! The correct pref-setting for switching off http/1.1 is 
"network.http.version" If you have not set this then by default it will be 
HTTP/1.0. 

Reporter: is this still happening?

Comment 6

[ruslan]

Squid doesn't work with 1.1, it's well known. The setting is 
netwerk.http.version=1.0. 1.0 + proxy.keep-alive enabled will actually work. 
This bug is invalid overall.

Comment 7

[Tom Everingham]

verified INVALID

Comment 8

[Jason Eager]

Oh no you don't. :P

I've set http version to 1.0 in debug->network, AND I've edited
prefs.js in my profile directory and added "netwerk.http.version=1.0" to
the file.

So I have both "network.http.version=1.0" AND "netwerk.http.version=1.0" in that
file.

ftp still doesn't work. I enter ftp://ftp.mozilla.org (and hit return) and the
browser just sits there. Doesn't do anything. Same thing happens if I click on a
ftp link.

Reopening the bug.

Comment 9

[Jason Eager]

Furthermore, if we KNOW this is going to be a problem with squid, then we need
to add a checkmark box to the proxy pane in preferences, something like "I use
squid as my proxy" which will set the http version back down to 1.0

Comment 10

[Bradley Baetz]

Is this bug in squid fixed in later versions? Can anyone point me to a maillist
archive or something for this, so I can ask people to upgrade?

OTOH, if this is widespread (and squid is fairly widespread), then would it be
possible to use HTTP/1.0 for all ftp proxy connections? This (and the related
bugs #50353, #33122) really need to be fixed, or autodetected.

This bug isn't the same as those two though - I get #50353 even if I disable all
proxies, until I restart mozilla with them disabled, and can't access local
sites which don't use the proxy - thats probably what [e-mail] is seeing
now. This bug is probably dependant on those.

Doesn't MSIE use HTTP/1.1? Does that hit the squid bug, or does it avoid it in
some way?

Comment 11

[tenthumbs]

While some people may think Squid doesn't work with HTTP/1.1, it's just not true.
I can telnet to mine and feed it an ftp URL with all sorts of HTTP/1.1 headers,
and it always performs. More importantly, Squid proxies http URL's just fine; I
use it every day with Mozilla.

It's junkbuster that's busted.

Comment 12

[Gagan]

->rjc

Comment 13

[Robert John Churchill]

Try a tip build... a fix went in for proxy FTP late on the 6th.

Comment 14

[Tom Everingham]

verified