84694 - Proxy: Gauntlet errors (html) display as text.

Status: VERIFIED DUPLICATE of bug 83480

(Core :: Networking, defect, P3)

Description

[alanjstr]

When attempting to (incorrectly) go to bugzilla.org, a DNS failure error occurrs
(as it should).  But the error message that comes up is a bunch of html coding
(attachment available on request).  The error message appears to be the same as
if I try to go to the URL in IE 5 (screenshot also available upon request).

Comment 1

[alanjstr]

Attachment: What appears on the screen

Comment 2

[alanjstr]

Attachment: What it looks like in IE

Comment 3

[benc]

qa to me.
-> Networking

The DNS error is displayed in HTML because you are connecting to a proxy server.

If DNS failed and you were using a direct conection, you would receive a dialog
box w/ the error message. Proxy servers return errors to your browser via a HTTP
5xx code and put the message into the body as HTML.

Please describe the proxy preferences (or even better copy the "network.proxy.*"
prefs.

Once you verify this, please try to find out the proxy server type and vendor
name. (I did not see vendor information in the HTML you included.

Comment 4

[Doron Rosenberg (IBM)]

-> default netwerk owner, aka neeti

Comment 5

[alanjstr]

I am using an autoconfig proxy inside of Verizon.com.  HTTP can also be 
funnelled through proxy.verizon.com:80.  Is there something I can run that will 
query my proxy server to find out what its running?

Comment 6

[alanjstr]

The company proxy is Gauntlet.

Comment 7

[benc]

-qawanted, I'm on this one.

I saved the file and opened it as HTML, and it renedered on my NS6.0 for WinNT
system.

This might be a problem with the HTML headers of the response. Does anyone have
gauntlet system I can look at, or do you want to try to trap the response
headers yourself?

Comment 8

[Chase Tingley]

this looks liks a dup of 83480.

Comment 9

[alanjstr]

I agree, its the same thing, just a different brand of proxy server.  Why on 
earth they don't configure the proxy servers to return correct HTML is beyond 
me.  But since all the other browsers seem to know what to do, I guess its up 
to Mozilla to kludge it too :-( 

*** This bug has been marked as a duplicate of 83480 ***

Comment 10

[benc]

Any HTML experts able to explain why this doesn't render? If so, I can create
and evangelism bug and sic them on the vendor.