Closed
Bug 128045
Opened 23 years ago
Closed 23 years ago
connecting localhost IMAP does not work anymore
Categories
(Core :: Networking, defect)
Tracking
()
RESOLVED
FIXED
mozilla0.9.9
People
(Reporter: andre, Assigned: bbaetz)
References
Details
Attachments
(1 file)
1.15 KB,
patch
|
dougt
:
review+
darin.moz
:
superreview+
blizzard
:
approval+
|
Details | Diff | Splinter Review |
b: all builds from est. 20020218 to current (2002-02-26) os: wXP for about a week now I am completely unable to connect through my tunneled ports on wXP, I get "connection refused" messages, although that's not true POP und IMAP to other IPs seems to work 127.0.0.1 didn't work either If I could remember how to turn mozillas logging functions using envvars on, I could give more information
Assignee | ||
Comment 1•23 years ago
|
||
Do you have proxies enabled (specifically, a socks proxy)?
Assignee | ||
Comment 2•23 years ago
|
||
Doh! Making this work was part of the design on the new proxy stuff, except that I stuffed up the condition. Taking, and patch coming, tested with news and imap. Trivial patch, wanting for 0.9.9.
Assignee: mscott → bbaetz
Target Milestone: --- → mozilla0.9.9
Assignee | ||
Updated•23 years ago
|
Status: NEW → ASSIGNED
Component: Mail Back End → Networking
Product: MailNews → Browser
QA Contact: esther → benc
Assignee | ||
Comment 3•23 years ago
|
||
Comment 4•23 years ago
|
||
Comment on attachment 71757 [details] [diff] [review] patch sr=darin (yikes!)
Attachment #71757 -
Flags: superreview+
Updated•23 years ago
|
Attachment #71757 -
Flags: review+
Comment 5•23 years ago
|
||
r=dougt
Assignee | ||
Comment 6•23 years ago
|
||
*** Bug 127977 has been marked as a duplicate of this bug. ***
Assignee | ||
Comment 7•23 years ago
|
||
*** Bug 128064 has been marked as a duplicate of this bug. ***
Assignee | ||
Comment 8•23 years ago
|
||
Actually, I attached this patch to the wrong bug - meant to do it to bug 128064. Do you have proxies enabled? If not, then this is not the solution to your problem
Reporter | ||
Comment 9•23 years ago
|
||
Yes, I have been using proxy support (Socks 5 w/o auth), now after switching back to direct connection it works again. Socks worked with the browser component, seems to be horked for mailnews only (and for localhost only)
Assignee | ||
Comment 10•23 years ago
|
||
Were you using a pac file? Or an http proxy? IF so, then this patch will help you.
Assignee | ||
Comment 11•23 years ago
|
||
... or a socks proxy on another machine without localhost being in the 'don't proxy for' part of the manual proxy settings.
Updated•23 years ago
|
Blocks: 122050
Keywords: mozilla0.9.9+
Comment 12•23 years ago
|
||
Comment on attachment 71757 [details] [diff] [review] patch a=blizzard on behalf of drivers for 0.9.9
Attachment #71757 -
Flags: approval+
Reporter | ||
Comment 13•23 years ago
|
||
no http, no pac, just socks... I've added localhost to the "no-proxy for" list and it works again, maybe this is worth a release note if behaviour stays this way.
Assignee | ||
Comment 14•23 years ago
|
||
OK, in that case this one is invalid. I have added text for the 099 relnotes. In any event, I'll check this in when the tree opens.
*** Bug 128234 has been marked as a duplicate of this bug. ***
Assignee | ||
Comment 16•23 years ago
|
||
Checked in.
Status: ASSIGNED → RESOLVED
Closed: 23 years ago
Resolution: --- → FIXED
Comment 17•23 years ago
|
||
We should have done what is suggested in bug 31510 along time ago (just put "localhost, 127.0.0.1" into the no proxy field via all.js...
You need to log in
before you can comment on or make changes to this bug.
Description
•