Difference between revisions of "SecureFlag"

Jump to: navigation, search
m (Made ASP.NET as sub section of Setting the Secure Flag)
Line 11: Line 11:
= Setting the Secure Flag<br> =
= Setting the Secure Flag<br> =
<httpCookies requireSSL="true" />
<httpCookies requireSSL="true" />

Revision as of 14:10, 9 January 2013

This article is a stub. You can help OWASP by expanding it or discussing it on its Talk page.


The secure flag is an option that can be set by the application server when sending a new cookie to the user within an HTTP Response. The purpose of the secure flag is to prevent cookies from being observed by unauthorized parties due to the transmission of a the cookie in clear text.

To accomplish this goal, browsers which support the secure flag will only send cookies with the secure flag when the request is going to a HTTPS page. Said in another way, the browser will not send a cookie with the secure flag set over an unencrypted HTTP request.

By setting the secure flag, the browser will prevent the transmission of a cookie over an unencrypted channel.

Setting the Secure Flag


<httpCookies requireSSL="true" />

Testing for the Secure Flag

Related Articles

Testing for Cookie Attributes