Closed Bug 14490 Opened 25 years ago Closed 22 years ago

Proxies in viewer not working

Categories

(Core :: Networking, defect, P3)

x86
Linux
defect

Tracking

()

VERIFIED WONTFIX
Future

People

(Reporter: BenB, Assigned: gagan)

References

Details

Error: "Failed to get the HTTP proxy server" at file nsHTTPHandler.cpp, line 121 Break: at file nsHTTPHandler.cpp, line 121 Error: Can't load: http://www.yahoo.com/ (804b000d) I imported prefs from 4.6 and they're working on apprunner.
Status: NEW → RESOLVED
Closed: 25 years ago
Resolution: --- → FIXED
Target Milestone: M11
should work with my last checkin. pl. update mozilla/netwerk/protocol/http/src/nsHTTPHandler.cpp and verify. Thx.
I still get Error: Can't load: http://www.bucksch.com/ (804b000d) but no Error. (Apprunner doesn't start since sunday, so I hope, it's not just a problem with my install, but Viewer seems to work apart from proxies.)
Before you ask: Yes, my prefs seem to be OK :-)
Status: RESOLVED → REOPENED
Verified this: The problem persists.
Resolution: FIXED → ---
Clearing FIXED resolution due to reopen.
Target Milestone: M11 → M12
m12
QA Contact: tever → mozilla
QA Contact: mozilla → tever
Gagan, if you or one of your team members can assist me (giving me the big picture and/or pointing me to docs), I'm willing to do the implementation.
Moving Assignee from gagan to warren since he is away.
Should bug #20400 depend on this?
Moving what's not done for M12 to M13.
Bulk move of all Networking-Core (to be deleted component) bugs to new Networking component.
Assignee: warren → gagan
Target Milestone: M13 → M20
We don't care about viewer for now. -> M20 -> Gagan
Target Milestone: M20 → Future
Blocks: 61691
mass move, v2. qa to me.
QA Contact: tever → benc
Update please!
This bug hasn't had a comment on its merits in 22 months. Viewer is a dead & gone component. There doesn't seem to be a reason to keep this bug open.
Status: NEW → RESOLVED
Closed: 25 years ago22 years ago
Resolution: --- → INVALID
It was nevertheless a valid bug.
It was nevertheless a valid bug.
Status: RESOLVED → REOPENED
Resolution: INVALID → ---
wontfix is the right resolution.
Status: REOPENED → RESOLVED
Closed: 22 years ago22 years ago
Resolution: --- → WONTFIX
thanks for reporting this, sorry about the long delay in cleanup.
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.