Closed
Bug 244918
Opened 22 years ago
Closed 13 years ago
Google search hangs 1-2 min before display results behind proxy server
Categories
(Core :: Networking: HTTP, defect)
Tracking
()
RESOLVED
WORKSFORME
People
(Reporter: dj, Unassigned)
Details
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.6) Gecko/20040206 Firefox/0.8
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.6) Gecko/20040206 Firefox/0.8
The result set from a google toolbar search takes up to 2 minutes. Results are
always displayed after a wait. A search from the Google main page is likewise
slow (but nominally faster). An identical search from IE (boo, hiss) returns
results in a few seconds.
I am behind a firewall and a proxy server (WebMarshall -- NetIQ). If I bypass
the proxy server, the search results are returned as quickly as in IE.
Therefore I believe the issue to be related to proxy services. Mozilla 1.6 is
likewise slow but I did not test it outside the proxy server.
Reproducible: Always
Steps to Reproduce:
1. Install WebMarshall demo software with default settings. (
http://www.netiq.com/products/wma/trial.asp )
2. Set Firewall policies to allow HTTP/HTTPS/FTP connections from the proxy
server only. (may require two policies one to accept proxy server and one to
deny all others)
3. Attempt a search from Google Toolbar
Actual Results:
no search results displayed for 1-2 minutes. Eventually results are always
displayed. Same search with Mozilla 1.5 & 1.6 has similar results. Same search
under IE responds in a few seconds.
Expected Results:
Responsive result in seconds
This is preventing me from deploying Firefox/Mozilla as default browser for my
company (70+ employees).
Oh, and you guys rock! Thanks.
Updated•22 years ago
|
Assignee: p_ch → darin
Component: Search → Networking: HTTP
Product: Firefox → Browser
QA Contact: core.networking.http
Version: unspecified → Trunk
Comment 1•22 years ago
|
||
are you using a proxy autoconfiguration file (PAC file)? if so, how does it look?
| Reporter | ||
Comment 2•22 years ago
|
||
(In reply to comment #1)
> are you using a proxy autoconfiguration file (PAC file)? if so, how does it look?
We configure each machine manually. Each workstation is set up for IE initially
and then I install Firefox and configure the proxy settings down the line.
(http, ntp, gopher, ftp, socks, etc.) I set it to exclude the loopback i/f and
the subnet.
Thanks and sorry for the delay in response.
Dennis
Comment 3•22 years ago
|
||
you have an http _and_ a socks proxy??
| Reporter | ||
Comment 4•22 years ago
|
||
(In reply to comment #3)
> you have an http _and_ a socks proxy??
No, just an http proxy (http, https, ftp). My reference was to the manual proxy
configuration screen that details proxy settings for the various protocols.
Sorry for the lack of clarity.
Dennis
The same is hapening to me: Firefox (all versions)/Deep Park, Windows 2K. The
proxy is WebMarshall too, so this could be an issue with the way this proxy works.
Comment 7•20 years ago
|
||
This is an automated message, with ID "auto-resolve01".
This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.
While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.
If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.
The latest beta releases can be obtained from:
Firefox: http://www.mozilla.org/projects/firefox/
Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html
Seamonkey: http://www.mozilla.org/projects/seamonkey/
A fix for WebMarshall proxy server:
- open "about:config" in the URL bar.
- search for "network.http.proxy.version"
- change it's value to 1.0
Rationale:
WebMarshall has problems handling HTTP 1.1 connections (enabling HTTP 1.1 in Internet Explorer results in similar behavior).
Comment 10•20 years ago
|
||
Hmmm.... Early returns look promising. It didn't work at first but I'm having better luck after blowing away my profile.
Updated•20 years ago
|
Assignee: darin → nobody
Comment 11•20 years ago
|
||
(In reply to comment #10)
> Hmmm.... Early returns look promising. It didn't work at first but I'm having
> better luck after blowing away my profile.
>
Not that anyone cares about this obscure bug, but this didn't do the trick. It's still ultimately unusable at work.
Comment 12•17 years ago
|
||
Is this still an issue ?
Comment 13•15 years ago
|
||
I works fine with the current Firefox 4 beta 9.
Comment 14•13 years ago
|
||
thanks dguerrero. WFM per comment 13
Status: UNCONFIRMED → RESOLVED
Closed: 13 years ago
Resolution: --- → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•