212206 - redirection to secure pages (https) fails

Status: RESOLVED WORKSFORME

(SeaMonkey :: General, defect)

Description

[Fernando Goñi]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.4) Gecko/20030624
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.4) Gecko/20030624

Every time I try to access my amazon orders page (which is an https page through
redirection) using the secure server I get a "www.amazon.com could not be found.
Please check the name and try again" but it works OK woth IE6!!

Reproducible: Always

Steps to Reproduce:
1. www.amazon.com
2. Select "Your Account" 
3. Select "View or change your 1-click settings"
4. Input user + password.
5. Click on "Sign in using our secure server"

Actual Results:  
I always get the same message : "www.amazon.com could not be found. Please check
the name and try again"

Expected Results:  
Accessing my personal settings

I am in a LAN which access Internet through a Proxy Server

Comment 1

[Olivier Cahagne]

can you get to this URL ?
https://www.amazon.com/exec/obidos/subst/home/home.html/002-4565316-9502425

Comment 2

[Fernando Goñi]

No I cannot access this URL. I got the same error message (but I can access it 
with IE6)

Comment 3

[Olivier Cahagne]

are you using a proxy ?

Comment 4

[Fernando Goñi]

Yes. I am using Sygate security agent as personal firewall (but I can disable it
and the problem persist) and the LAN where I am working on is a big corporate
LAN and they are using a proxy which has to be accessed by means of
user+password (no idea which one but I can ask...)

Comment 5

[Olivier Cahagne]

did you make sure you have the same proxy set for HTTP and HTTPS ? Using auto
proxy (through a .pac file) ?

Comment 6

[Fernando Goñi]

Now it works. The problem was, as Olivier pointed out, due an autoproxy .pac
file that did not configure the SSL proxy for Mozilla in my company. I have
configured it manually and it works. How about an option like in IE6 "Use the
same proxy for all protocols"?

Comment 7

[Olivier Cahagne]

reopening as no specific patch fixed this issue

Comment 8

[Olivier Cahagne]

wfm

check bug 50380 for the pref.