Closed Bug 70013 Opened 24 years ago Closed 24 years ago

HTTP proxy doesn't seem to work - even in HTTP 1.0

Categories

(Core :: Networking: HTTP, defect)

Product:
Core
Component:
Networking: HTTP
Platform:
x86
Linux
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

()

Status:
VERIFIED INVALID

People

(Reporter: gila, Assigned: darin.moz)

Details

To reproduce this bug, install junkbuster which can be found at http://internet.junkbuster.com/ and configure mozilla's http proxy to go through localhost:5865 or the appropriate port for the junkbuster installation. Then browse this url: http://internet.junkbuster.com/cgi-bin/show-proxy-args The request should be blocked by junkbuster, but it is not, and instead goes directly through to the junkbuster.com server. Setting the HTTP version to '1.0' in the debug properties and restarting does not change this behavior. To test if the proxy is working, start netscape (or another browser which supports proxies), configure it, and browse the above url. It correctly shows the current junkbuster configuration.
Changed product to "Browser".
Assignee: wtc → darin
Component: NSPR → Networking: HTTP
Product: NSPR → Browser
QA Contact: wtc → tever
Version: 3.0 → other
Reporter what build are you using?
bug 38488 is the tracking bug for junkbuster issue with http1.0
Mozilla/5.0 (X11; U; Linux 2.4.1 i686; en-US; 0.8) Gecko/20010215 build id: 2001021503
Bug #38488 implies that it's possible to use junkbuster. I've set my debug prefs to http 1.0, verified that it's sending http 1.0 headers by checking it against a local webserver, and junkbuster DOES NOT WORK.
I think what you really have to do to make Mozilla work with Junkbuster is to disable KeepAlive in that Debug/Networking pref. Does it work then? I'm using Mozilla and Junkbuster for months now without problems, and I have the following settings: KeepAlive disabled, HTTP pipelineing enabled, HTTP version 1.1.
D'oh! It works now - as with 99% of computer problems, user error. I specified the proxy incorrectly as ip:localhost:5865 port: instead of ip:localhost port:5865 Should this bug be marked as 'invalid'? However, it would be nice if mozilla spit out some kind of warning that your proxy settings are bad rather than just ignoring them....
There is another bug for that :) Marking INVALID. Thanks for checking back.
Status: UNCONFIRMED → RESOLVED
Closed: 24 years ago
Resolution: --- → INVALID
Verified invalid. See also bug 38488.
Status: RESOLVED → VERIFIED
QA Contact: tever → junruh
You need to log in before you can comment on or make changes to this bug.