Closed
Bug 522704
Opened 15 years ago
Closed 14 years ago
Firefox shows generic proxy information insteed of planned info.
Categories
(Firefox :: General, defect)
Tracking
()
RESOLVED
WORKSFORME
People
(Reporter: thorin18, Unassigned)
Details
(Whiteboard: [CLOSEME 2010-12-01])
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.0.14) Gecko/2009090905 Fedora/3.0.14-1.fc10 Firefox/3.0.14
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.0.14) Gecko/2009090905 Fedora/3.0.14-1.fc10 Firefox/3.0.14
We have a proxy.pac file and since new version (3.5 and 3.0.12) came out firefox doesn't show our info that we setup on the proxy it just came up with the generic browser info that this request cannot be finished due to proxy problems.
Reproducible: Always
Steps to Reproduce:
1. We block a PC on the proxy
2. Opening browser and on every page is the same error generic firefox insteed of our message to users.
Actual Results:
getting the browser message
Expected Results:
show our proxy message
It was ok in firefox before version 3.0.12 as I can recall. something had been changed and now we got this problem as it's not so clear for users that we cut their internet for a reason.
Comment 1•15 years ago
|
||
How did you block the PC ? With what error response ?
You don't need to "block" PCs. Simply configure a FF 2.0.0.19 (works OK) and FF 3.5.5 (displays "generic" messages) to use both an HTTP- and an SSL-Proxy (squid).
Then visit the following urls:
(a) https://www.example.com:8443
FF2: displays the proxy response (OK)
FF3: displays an internal error page (not OK)
(b) http://www.example.com:8080/
FF2: displays the proxy response (OK)
FF3: displays the proxy response, too (OK)
FF3 does behave inconsistently.
(In reply to comment #1)
> How did you block the PC ? With what error response ?
Well we use squid to do it. we set a proper acl to lock them out, we do this to get what we want :) ppl without internet are willing to do anything to get it back.
I will do screens how should it look like and how it does.
Comment 4•15 years ago
|
||
For reference, you should see :
- bug 482874
- bug 479922
- <http://curtisb.posterous.com/404-error-page-status-0>
- <https://wiki.mozilla.org/Firefox/Projects/Network_Error_Pages>
Webbrowsers will sometimes override the error page from the webserver (404 Not found, etc) and replace it with a built-in error page (to make it more fancy, or to provide extra tools on the error page). At the same time, they try to detect if the webserver send back some customized error page (different from the default), in which case they wouldn't do this. Internet Explorer and Chrome apparently check the length of the error page to make this decision. Some websites add extra (blank) lines in the error message to avoid this.
Note that some proxyservers also try to do the same thing, my proxyserver at works replaces the 404 error page every time, while the one at home replaces it sometimes.
I'm not sure what the difference is between FF2 and FF3, or why the error page in different in your 2 testcases, but it will change even more in the future.
Od thing, but seems that since 3.5.5 and 3.0.15 it's working fine again...
I will monitor this with next updates and see if I have any unupdated PCs here with older version...
thanks for help anyway :)
Comment 6•14 years ago
|
||
Reporter, please retest with Firefox 3.6.12 or later in a fresh profile (http://support.mozilla.com/kb/Managing+profiles). Also update your plugins (flash, adobe reader, java, quicktime, silverlight, etc.) Go to the developer's website and download the latest version from there. If you no longer see this issue, please close this bug as RESOLVED, WORKSFORME. If you do see the bug, please post a comment.
Whiteboard: [CLOSEME 2010-12-01]
Comment 7•14 years ago
|
||
No reply, INCOMPLETE. Please retest with Firefox 3.6.12 or later and a new profile (http://support.mozilla.com/kb/Managing+profiles). If you continue to see this issue with the newest firefox and a new profile, then please comment on this bug.
Status: UNCONFIRMED → RESOLVED
Closed: 14 years ago
Resolution: --- → INCOMPLETE
I am sorry for the delay! this was resolved! closing as resolved!
Resolution: INCOMPLETE → FIXED
Updated•14 years ago
|
Resolution: FIXED → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•