Closed Bug 59113 Opened 25 years ago Closed 24 years ago

chrome://foo.js requests send to auto-loaded proxy

Categories

(Core :: Networking, defect, P3)

x86
Linux
defect

Tracking

()

VERIFIED WORKSFORME

People

(Reporter: utx, Assigned: gagan)

Details

If proxy auto-load is on, mozilla asks proxy for internal chrome://foo.js requests - these requests fail, because most proxies (at least with my wwwoffled) doesn't know how to serve these requests, and mozilla stops work complaining about error while loading chrome://foo. Note that manual proxy configuration doesn't have this bug. Choose a working proxy with proxy auto-load page (if you don't have, you can try wwwoffle ftp://ftp.demon.co.uk/pub/unix/httpd). Choose proxy auto-load in proxy setup. Try any www page. Mozilla writes error messages and does nothing: got a request JavaScript error: line 0: uncaught exception: [Exception... "Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsIBrowserInstance.loadUrl]" nsresult: "0x80004005 (NS_ERROR_FAILURE)" location: "JS frame :: chrome://navigator/content/navigator.js :: OpenBookmarkURL :: line 693" data: no]
Browser, not engine. Reassigning to Networking for further triage -
Assignee: rogerl → gagan
Component: Javascript Engine → Networking
QA Contact: pschwartau → tever
Reporter is this still a problem in the latest nightlies?
I am marking this WORKSFORME because of the lack of response to this bug, both from the reporter, and from the component this was assigned too. Reporter, please feel free to reopen anytime if you are still seeing this in a nightly build (http://ftp.mozilla.org/pub/mozilla/nightly), or wait a few days for Mozilla 0.7. Thank you! Fabian.
Status: UNCONFIRMED → RESOLVED
Closed: 25 years ago
Resolution: --- → WORKSFORME
reporter: This bug is a "futured" or "untargeted" bug which has been "resolved/works for me". Most bugs meeting this criteria are usually somewhat out of date or working in the current builds. If this bug is not happening for you in a recent build (such as the Mozilla daily build, Mozilla 0.9.3, or Netscape 6.1), please use the friendly "Mark bugs as VERIFIED" radio button to set this bug to "VERIFIED/WORKS FOR ME" If you reported the bug on a platform (e.g. Linux) and other contributors reported on another platform (e.g. Mac OS), please comment that it works for you but do not verify it yet. For these multi-platform bug reports, we need to verify all reported platforms -OR- create new "still broken on platform X" bugs when you verify.
It works with my WWWOFFLE proxy correctly.
Status: RESOLVED → VERIFIED
I am not sure if I was followed Instructions correctly. I am marking it as closed.
Status: VERIFIED → CLOSED
Please don't mark any bug as closed, thanks! Verified is the last stage for a bug currently. Reopening to mark as verified again, sorry for the spam.
Status: CLOSED → UNCONFIRMED
Resolution: WORKSFORME → ---
Marking WORKSFORME again
Status: UNCONFIRMED → RESOLVED
Closed: 25 years ago24 years ago
Resolution: --- → WORKSFORME
and VERIFIED worksforme.
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.