Forum Moderators: DixonJones
There is a cookie called when the visitor accesses pages on the main site and a different cookie when they access the SSL site, and we'd like to know how to make it so that the same cookie is called for both.
If that is not possible, I'd like to know how people handle this problem.
The SSL site and the main sites are hosted on the same server running IIS, written in asp and html.
Could you point me in the direction of a solution or let me know what you are doing about this?
You could also pass the original cookie value in a query string as they go to the secure site. Embed this into the order form, or set the value into the SSL site's cookie.
Note: Redirecting users (after ordering) to a thank you page on the original site will avoid the 3rd party cookie issue altogether.
<a href="secure.asp" onClick="top.location.href='secure.asp?value=' + cookiecontent; return false">Secure Order Form</a>
2. Since you're using ASP, you can then embed the query string into a hidden field on your order form:
<%=Request.Querystring("value")%>