827572 - Unable to access subdomains of an ssl-domain

Status: RESOLVED INCOMPLETE

(SeaMonkey :: Location Bar, defect)

Description

[Diana K.]

User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20100101 Firefox/17.0
Build ID: 20121128204232

Steps to reproduce:

I do have 2 sub-domains pointing to the same IP-address: sub2.domain.com is accessible via HTTP and HTTPS, sub1.sub2.domain.com only via HTTP.
Since SeaMonkey 2.13 or 2.14 when calling http://sub1.sub2.domain.com/ SeaMonkey tries to fetch https://sub1.sub2.domain.com/ (Note: HTTPS)



Actual results:

Fetching https://sub1.sub2.domain.com/ fails with ssl_error_bad_cert_domain because there is only an SSL-certificate for sub2.domain.com available.

I've tried it with all plugins disabled in safe-mode, but I'm still not able to access this domain. Firefox 17.0.1 does not have any problems.
Any ideas? It looks like SeaMonkey is doing an internal rewrite from HTTP to HTTPS, because there is no single entry in the webservers logfile nor any entry at livehttpheaders or firebug.


Expected results:

Content of http://sub1.sub2.domain.com/ should have been fetched.

Comment 1

[Matthias Versen [:Matti]]

Please clear the disk cache and try it again

Comment 2

[Diana K.]

I am not using disk cache (browser.cache.disk.enable is set to false).
about:cache shows always 0 KiB for "Storage in use" at "Offline cache device".

Is there any other configuration/cache which could do this even when starting SeaMonkey in safe-mode?

Comment 3

[Matthias Versen [:Matti]]

Is that an internal domain or can you provide the real URLs for testing ?
Note: Seamonkey and Firefox should behave identical if you use matching versions

Comment 4

[Diana K.]

These are internal domains.
Just updated SeaMonkey to 2.15, same effect. Updated Firefox to 18, still working.

LiveHTTPHeaders is showing:
#request# GET http://sub1.sub2.domain.com/ 
#request# GET https://sub1.sub2.domain.com/ 

As far as I know #request# means the answer is sent from cache.

Firebug is showing:
GET http://sub1.sub2.domain.com/, loading-wheel on timeline always spinning
GET https://sub1.sub2.domain.com/, status aborted

Comment 5

[Matthias Versen [:Matti]]

Please create a http log and attach it here
https://developer.mozilla.org/en-US/docs/HTTP_Logging
(replace Firefox.exe with Seamonkey.exe)

This should show why SM switches to https unless the redirect is done via meta tag or JS in the page.

Comment 6

[Philip Chee]

Diana, does this also affect Firefox 17?

Comment 7

[Phoenix]

Resolved per whiteboard