Closed
Bug 160091
Opened 23 years ago
Closed 22 years ago
localhost or 127.0.0.1 hosts do not bypass proxy settings
Categories
(Camino Graveyard :: General, defect)
Tracking
(Not tracked)
VERIFIED
WORKSFORME
People
(Reporter: d.c.burgess, Assigned: saari)
References
Details
Trying to access local files through the inbuilt web server results in a 'host
not found' error from the proxy server. (Chimera 0.4)
Comment 1•23 years ago
|
||
WFM Mac OS X 10.1.5, Chimera 0.4, Privoxy 2.9.14 @ 127.0.0.1:8118 enabled
(http://localhost/~nik/, http://127.0.0.1/~nik/).
| Reporter | ||
Comment 2•23 years ago
|
||
Mac OS X 10.1.5, Chimera 0.4, proxy not on local machine
| Reporter | ||
Comment 4•23 years ago
|
||
It *does* happen using Mozilla (1.1b), unless I specify to bypass localhost in 'Preferences>
Advanced>Proxies>No Proxy For'. I am unable to add localhost to the Mac OS X 'System
Preferences>Network>Proxies>Bypass Proxy Settings for these Hosts & Domains' to enable a
workaround for Chimera.
Comment 5•23 years ago
|
||
Same thing here. I have Apache and Mozilla 1.1b or nightly running on localhost
and use SmartCache as proxy. Mozilla always tries to go via SmartCache.
Using proxy for localhost should at least be configurable (checkbox)
Fixing bug 31510 might make this work the way people want (realistically, what
sensible end-power user would WANT to proxy localhost|127.0.0.1 ?
Depends on: 31510
| Reporter | ||
Comment 7•23 years ago
|
||
This seems to be resolved by Mac OS X 10.2 Jaguar which allows 127.0.0.1 and
localhost to be added to the 'Bypass Proxy Settings for these Hosts & Domains'
in System Preferences > Network > Proxies. Still an issue with Mac OS X 10.1.x.
(Chimera 0.5, Mac OS X 10.2.1)
Was there a problem with how Mac OS 10.1.x allowed "no proxy?" (wondering what
the change is)
Comment 9•22 years ago
|
||
reopen if it happens with a trunk build.
Status: NEW → RESOLVED
Closed: 22 years ago
Resolution: --- → WORKSFORME
Comment 10•20 years ago
|
||
V/wfm.
Camino 2005091409 (v1.0a1).
Safari seems to automatically allow connections to localhost (or perhaps 127.0.0.1).
Status: RESOLVED → VERIFIED
You need to log in
before you can comment on or make changes to this bug.
Description
•