up vote 0 down vote favorite
share [g+] share [fb]

I'm having trouble finding a concrete explanation online anywhere. We have a UAT (testing) environment that issues a self-signed SSL certificate. Because this is obviously not a valid SSL certificate, IIS doesn't seem to be sending cookies for HTTP responses for our UAT domain.

Can anyone confirm this is expected behaviour? If not, does anyone know how to ensure cookies are correctly written into the HTTP response?

Our web server platform is IIS7.5 with ASP.NET in Integrated Mode.

Our LIVE environment which has a valid SSL certificate does not exhibit this same issue.

link|improve this question
Have you tried adding this certificate to a trusted list, so when you browse the page (if there are any) in browser it does not show you any warnings? In my own experience cookies always worked well regardless of certificate origin as long as browser accepts such self-signed certificate (I'm referring to browsing "normal" website in a browser -- don't know if web services will do any difference). – LazyOne Aug 22 '11 at 16:17
feedback

Know someone who can answer? Share a link to this question via email, Google+, Twitter, or Facebook.

Your Answer

 
or
required, but never shown
discard

Browse other questions tagged or ask your own question.