Closed Bug 197697 Opened 22 years ago Closed 9 years ago

Proxy: client->proxy connection establishment timeout is "The operation timed out when attempting to contact <host>."

Categories

(Core :: Networking, defect)

Product:
Core
Component:
Networking
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

()

Status:
RESOLVED WONTFIX

People

(Reporter: benc, Unassigned)

References

(
URL
)

Details

(Keywords: user-doc-needed)

(whoops) Followup to bug 56629. STEPS: Configure proxy to an address that is not in use. When you make a request, the proxy connection attempt will timeout. EXPECTED: An error similar to what was done in bug 56629. "Your proxy connection timeed out".
.
Assignee: dougt → darin
Status: NEW → ASSIGNED
Target Milestone: --- → Future
-> default owner
Assignee: darin → nobody
Status: ASSIGNED → NEW
QA Contact: benc → networking
Target Milestone: Future → ---
This error is misleading for users who configure configure a corporate proxy server, then forget that it's set. The connection to the proxy times out, but the error message implies that a connection to the site itself times out. Is there a chance of getting this fixed?
Flags: wanted1.9.1?
Keywords: user-doc-needed
This already missed 1.9.1 string freeze, but seems like we should get tin 1.9.2 (though I doubt it'll block). I'm guessing there's some user confusion which is why it came up?
Flags: wanted1.9.2?
Flags: wanted1.9.1?
Flags: blocking1.9.2?
Flags: blocking1.9.2? → blocking1.9.2-
:bagder is doing some separate work to help with the issue of proxies when migrating between locations
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.