Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    text
    copied!<p>2A The cookie path is the path on the server the cookie relates to, not the path where the cookie is store.</p> <p>From <a href="http://www.quirksmode.org/js/cookies.html" rel="nofollow noreferrer">http://www.quirksmode.org/js/cookies.html</a></p> <blockquote> <p>The path gives you the chance to specify a directory where the cookie is active. So if you want the cookie to be only sent to pages in the directory cgi-bin, set the path to /cgi-bin. Usually the path is set to /, which means the cookie is valid throughout the entire domain. This script does so, so the cookies you can set on this page will be sent to any page in the www.quirksmode.org domain (though only this page has a script that searches for the cookies and does something with them).</p> </blockquote> <p>You are using ASP.Net. Also see the "CookieLess" Session and Authenication options e.g. <a href="http://msdn.microsoft.com/en-us/library/system.web.security.formsauthentication.formscookiepath.aspx" rel="nofollow noreferrer">http://msdn.microsoft.com/en-us/library/system.web.security.formsauthentication.formscookiepath.aspx</a> If you are worried about cookies. This uses a URL session ID instead to track your session.</p> <p>You can also use a SQL Server to track session state or a State server. e.g.</p> <pre><code>&lt;sessionState mode="SQLServer" sqlConnectionString="SQLSessionDB" cookieless="false" timeout="65" cookieName="MSESSID"/&gt; </code></pre> <p>1A. SSL encrypts transport. Hence your cookies will be less likely to be stolen on route to the client or back. That doesn't mean a malicious program on the client computer can't steal it. This is very unlikely though.</p>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload