This is because the cookie domain is actually domain.com:PORT_NUMBER which is DIFFERENT than domain.com. The same goes for http://domain.com:PORT_NUMBER. Using these types of URLS is currently not supported until this is fixed.

Comments

crystaldawn’s picture

crystaldawn commented

Notes on this situation: The cookie issue goes away after you login and then logout of the SSL domain (not the nonssl domain) for the first time. Weird. Anyways, I am leaving it up in case others run into the same issue. To fix it all I had to do was login, logout, and then all subsequent calls worked just fine. So, I then tried it on another computer that had NOT been to the test site yet and again I had the same issue. So I tried the login/out trick and it fixed the issue and I could not get it to NOT work again unless I cleared the cookies. I am not sure whats causing it to do this just yet.

crystaldawn’s picture

crystaldawn commented
Status: Active » Closed (won't fix)

I've never encountered a use for this anyway.