Closed
Bug 586908
Opened 14 years ago
Closed 14 years ago
Infinite requests when proxy from system settings is redirected
Categories
(Core :: Networking, defect)
Tracking
()
RESOLVED
FIXED
mozilla2.0b7
Tracking | Status | |
---|---|---|
blocking2.0 | --- | final+ |
blocking1.9.2 | --- | - |
status1.9.2 | --- | .13-fixed |
status1.9.1 | --- | unaffected |
People
(Reporter: john.p.baker, Assigned: bjarne)
References
Details
(Keywords: regression)
Attachments
(2 files, 3 obsolete files)
4.74 KB,
patch
|
bjarne
:
review+
christian
:
approval1.9.2.13+
|
Details | Diff | Splinter Review |
4.77 KB,
patch
|
bjarne
:
review+
|
Details | Diff | Splinter Review |
Our IE PAC file used to be served from http://www.bristol.ac.uk/xyz.pac (name changed). Several years ago it was changed to http://wwwcache.bris.ac.uk/cgi-bin/proxy.pl and a redirect put in place from the previous URL. As we update Firefox, in the summer break, to a version defaulting to 'use system settings' for the proxy configuration, we have found some that have the old URL configured and, when Firefox is started, they will continually try to fetch the old PAC script (one last week 2 million times over a 7 hour period, one this week with 4.5 million requests) rather than use the new one.
Assignee | ||
Comment 1•14 years ago
|
||
Do I understand you correctly: If I point FF to a URL which redirects to a PAC-file, then it loops forever? Version of FF?
Reporter | ||
Comment 2•14 years ago
|
||
(In reply to comment #1) > Do I understand you correctly: If I point FF to a URL which redirects to a > PAC-file, then it loops forever? Version of FF? Not quite; If you set your system setting to a PAC URL which redirects and set Firefox to use system setting then it loops forever. The PC systems team replicated on 3.6.0 and 3.6.8 - we haven't tried trunk yet; IIRC the _default_ setting was switched around 3.6.4 release.
Assignee | ||
Comment 3•14 years ago
|
||
Reproduced. Nominating for blocking.
blocking1.9.2: --- → ?
blocking2.0: --- → ?
Updated•14 years ago
|
Assignee: nobody → jduell.mcbugs
blocking2.0: ? → final+
Updated•14 years ago
|
Assignee: jduell.mcbugs → bjarne
Assignee | ||
Comment 4•14 years ago
|
||
The problem here was that the redirected channel was trying to resolve its proxy, picked up the uri from system settings, and thus got itself into an endless loop. nsPACMan::AsyncOnChannelRedirect() makes sure to update |nsPACMan::mPACURI| appropriately, but the code in nsProtocolProxyService::Resolve_Internal() picks up the original uri from system settings and overwrites it.
Attachment #476156 -
Flags: review?(cbiesinger)
Assignee | ||
Comment 5•14 years ago
|
||
Adding timeless to CC-list since he did the work for bug #529773 and may have input here.
Comment 6•14 years ago
|
||
Comment on attachment 476156 [details] [diff] [review] Fix to avoid this problem r=biesi but please add a test
Attachment #476156 -
Flags: review?(cbiesinger) → review+
Comment 7•14 years ago
|
||
Not blocking 1.9.2.x but we'll approve a patch with a test if you set the appropriate approval flag.
Blocks: 529773
blocking1.9.2: ? → -
status1.9.1:
--- → unaffected
status1.9.2:
--- → wanted
Keywords: regression
Assignee | ||
Comment 8•14 years ago
|
||
Changed behaviour to return NS_OK immediately if the loop was discovered. Also added testcase for this particular problem.
Attachment #476156 -
Attachment is obsolete: true
Attachment #476368 -
Flags: review?(cbiesinger)
Attachment #476368 -
Flags: approval1.9.0.next?
Comment 9•14 years ago
|
||
Comment on attachment 476368 [details] [diff] [review] Slightly modified version w/ testcase +++ b/netwerk/base/src/nsProtocolProxyService.cpp Fri Sep 17 22:37:44 2010 +0200 + if (mPACMan && mPACMan->IsPACURI(uri)) return NS_OK; Please put the return on its own line, that makes debugging simpler (when stepping through or when setting a breakpoint) +// Ensure we're using system-properties Please indent comments to the same level as the code + if (failed) retval = failed; Should that be "failed" instead of failed?
Attachment #476368 -
Flags: review?(cbiesinger) → review+
Assignee | ||
Comment 10•14 years ago
|
||
Fixed up the last issues, carrying over the r+
Attachment #476368 -
Attachment is obsolete: true
Attachment #476379 -
Flags: review+
Attachment #476379 -
Flags: approval1.9.0.next?
Attachment #476368 -
Flags: approval1.9.0.next?
Updated•14 years ago
|
Attachment #476379 -
Flags: approval1.9.0.next? → approval1.9.2.11?
Comment 11•14 years ago
|
||
Comment on attachment 476379 [details] [diff] [review] Addressed comments from reviewer Approved for 1.9.2.11, a=dveditz for release-drivers
Attachment #476379 -
Flags: approval1.9.2.11? → approval1.9.2.11+
Assignee | ||
Comment 12•14 years ago
|
||
Seems like I forgot to request check-in... done. I believe the patch also applies to 1.9.2.
Keywords: checkin-needed
Comment 14•14 years ago
|
||
backed out on 1.9.2 due to failure in the new test added with this patch http://hg.mozilla.org/releases/mozilla-1.9.2/rev/ea16213ee93e http://tinderbox.mozilla.org/showlog.cgi?log=Firefox3.6/1285745534.1285745969.9046.gz
Comment 15•14 years ago
|
||
Comment on attachment 476379 [details] [diff] [review] Addressed comments from reviewer We'll need a new 1.9.2 patch that either fixes the test or fixes whatever bug in the backport the test is catching.
Attachment #476379 -
Flags: approval1.9.2.11+ → approval1.9.2.11-
Assignee | ||
Comment 16•14 years ago
|
||
I'll take a look. It didn't land on trunk yet?
Assignee | ||
Comment 17•14 years ago
|
||
The constant nsIProtocolProxyService::PROXYCONFIG_SYSTEM used by the test is undefined in 1.9.2. Test defaulted to DIRECT and failed in the cross-check to verify that redirection actually took place. Should be ok now. (Carrying over the r+ since this is just a simple change in the test.)
Attachment #479740 -
Flags: review+
Assignee | ||
Updated•14 years ago
|
Attachment #479740 -
Flags: approval1.9.2.11?
Assignee | ||
Comment 18•14 years ago
|
||
Fixed syntax-error in PAC-script which seems to have been forgiven by trunk, but just for completeness. Carrying over the r+.
Attachment #476379 -
Attachment is obsolete: true
Attachment #479742 -
Flags: review+
Comment 19•14 years ago
|
||
Comment on attachment 479740 [details] [diff] [review] Patch for 1.9.2 too late for 1.9.2.11, moving to next release.
Attachment #479740 -
Flags: approval1.9.2.11? → approval1.9.2.12?
Comment 20•14 years ago
|
||
With the tree in its current phase you'll probably need to actively look for a check-in buddy on IRC (or mail). The keyword alone might not get it into Firefox 4.
Comment 21•14 years ago
|
||
sorry, i was traveling on vacation for a month. but it looks like things are mostly in hand, minus the excitement of landing window hunts
Comment 22•14 years ago
|
||
Comment on attachment 479740 [details] [diff] [review] Patch for 1.9.2 a=LegNeato for 1.9.2.12. Please land only on the mozilla-1.9.2 default branch, *not* the relbranch.
Attachment #479740 -
Flags: approval1.9.2.12? → approval1.9.2.12+
Assignee | ||
Comment 23•14 years ago
|
||
Anything I need to do to move this one forward...?
Reporter | ||
Updated•14 years ago
|
Whiteboard: [needs landing]
Reporter | ||
Comment 24•14 years ago
|
||
It looks as if this was landed on trunk yesterday http://hg.mozilla.org/mozilla-central/rev/290ad164b656
Whiteboard: [needs landing] → [landed on trunk][needs landing on 1.9.2 branch]
Target Milestone: --- → mozilla2.0b8
Assignee | ||
Comment 25•14 years ago
|
||
This still needs landing on 1.9.2 ref comment #22. Should it be marked "fixed" anyway?
Reporter | ||
Updated•14 years ago
|
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → FIXED
Whiteboard: [landed on trunk][needs landing on 1.9.2 branch] → [needs landing on 1.9.2 branch]
Version: 1.9.2 Branch → Trunk
Comment 26•14 years ago
|
||
http://hg.mozilla.org/releases/mozilla-1.9.2/rev/b3d441310e5c
Keywords: checkin-needed
Whiteboard: [needs landing on 1.9.2 branch]
Target Milestone: mozilla2.0b8 → mozilla2.0b7
You need to log in
before you can comment on or make changes to this bug.
Description
•