Closed Bug 25217 Opened 25 years ago Closed 23 years ago

Proxy: browser attempts to resolve names

Categories

(Core :: Networking, defect, P3)

Product:
Core
Component:
Networking
Platform:
x86
Windows 98
Type:
defect

Tracking

()

Status:
RESOLVED WORKSFORME

People

(Reporter: jdrash, Assigned: gagan)

Details

Mozilla M13 does not exhibit the same behavior as Netscape when behind a firewall. It attempts to resolve the host name in the URL instead of just passing the URL to the proxy directly.
Assigning all open "nobody@mozilla.org" bugs to "leger@netscape.com" to weed thru.
Assignee: nobody → leger
Component: Browser-General → Networking
Pretty sure this is a dup. tever?
Assignee: leger → gagan
QA Contact: nobody → tever
proxies were not completely functional in M13. I would suggest you (reporter) try this with the latest builds. Reopen if you still see the problem.
Status: NEW → RESOLVED
Closed: 25 years ago
Resolution: --- → FIXED
I don't know about a dupe. Proxies have been working for a few weeks. Marking verified.
Status: RESOLVED → VERIFIED
M15 - shows same behavior. If using an automatic proxy configuration file, Mozilla tries to resolve the host name. (Same true for Netscape 6 PR1). If a manual proxy is used then Mozilla works fine.
Status: VERIFIED → REOPENED
Resolution: FIXED → ---
proxy auto config not in yet. dup of 20145 *** This bug has been marked as a duplicate of 20145 ***
Status: REOPENED → RESOLVED
Closed: 25 years ago → 25 years ago
Resolution: --- → DUPLICATE
bug has changed into DUP of 20145 - marking verified
Status: RESOLVED → VERIFIED
Once pack is working, I'll add a test that verifies we don't fire a DNS request when using PAC.
Summary: Browser attempts to resolve names behind a firewall → Proxy: browser attempts to resolve names
As of Mozilla 0.9.4 this behavior is fixed
Status: VERIFIED → CLOSED
(we don't close bugs...yet)
Status: CLOSED → REOPENED
Resolution: DUPLICATE → ---
maybe we'll figure out some process, like post Mozilla 1.0?!
Status: REOPENED → RESOLVED
Closed: 25 years ago → 23 years ago
Resolution: --- → WORKSFORME
QA Contact: tever → benc
You need to log in before you can comment on or make changes to this bug.