Closed
Bug 70919
Opened 24 years ago
Closed 24 years ago
redirection from http: to https: doesn't work
Categories
(Core :: Networking: HTTP, defect)
Core
Networking: HTTP
Tracking
()
VERIFIED
FIXED
mozilla0.9.1
People
(Reporter: rbremer, Assigned: darin.moz)
References
Details
We use a firewall/proxy system, which requires me to login before first use.
The proxy server is put in as manual proxy configuration, via DNS name and port
number 8080 for http, https and ftp services.
As soon as I hit a page the first time, it is redirecting me to an URL like this:
https://proxy/login.html?nexturl="http://www.mozilla.org"
I guess you get the idea.
Now, the mozilla browser is unable to follow that link, it will just sit there
without continuing. I always need to open good ole' netscape 4.75 and do it,
then I can use Mozilla to browse.
Is there anyway I can help you in tracking it down?
Thank guys,
Ronny
![]() |
||
Comment 1•24 years ago
|
||
Ronny, do you have a build that includes PSM? What does "Tasks -> Privacy and
Security -> Personal Security Manager" show?
Reporter | ||
Comment 2•24 years ago
|
||
Boris,
yes I do have a build with PSM.
Ronny
Reporter | ||
Comment 3•24 years ago
|
||
actually, I did some more testing, when I access SSL-enabled sites thru the
proxy server it is very slow, it takes like 5 minutes to get the redhat network
page displayed, the CPU goers up to 100% during that time and all mozilla
sessions are stuck until the page is fully displayed.
Maybe that helps.
Ronny
![]() |
||
Comment 4•24 years ago
|
||
Ronny, the bug you describe with SSL through a proxy being very slow has been
fixed recently (on Feb 21). Please update to a recent Mozilla build and give it
a try... That may or may not be related to the original problem you describe
Reporter | ||
Comment 5•24 years ago
|
||
Boris,
I tried the nightly build from 3/6, indeed, it is much faster with https thru a
proxy. Thanks for the info :)
Unfortunately, the redirection still doesn't work.
Ronny
Comment 6•24 years ago
|
||
I've recently seen another report of this but I can't find it. Setting bug
status to New.
Status: UNCONFIRMED → NEW
Ever confirmed: true
-->http
Assignee: neeti → darin
Component: Networking → Networking: HTTP
Assignee | ||
Comment 8•24 years ago
|
||
will be fixed along with 76866
Assignee | ||
Comment 9•24 years ago
|
||
fixed with http branch landing.
Status: ASSIGNED → RESOLVED
Closed: 24 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•