Secure cookies

Cookie is name and value pair simplified. Developer uses cookies to store data on the client side. This is handled using the programming language like PHP, Perl,…

In PHP you would define cookie like this:

setcookie( name, value, expire, path, domain, secure, httponly);

Cookies can be stolen via JavaScript but they may not be. It depends. The httponly flag, if set to true, means cookies cannot be altered via JavaScript.

The secure flag purpose is to prevent clear text cookies over HTTP. By setting the secure flag, the browser will prevent the transmission of a cookie over an unencrypted channel.

The other parameters like domain and path are constraints, that precisely set where cookie should work.

For instance setting cookie domain to www.example.com will mean only the exact domain www.example.com will be matched, while .example.com will also match any subdomain (forum.example.com, blog.example.com).

The path argument default value of / means every request will get the cookie, while /forum/ limits the cookie to just /forum path.

The expire flag is usually set to some period like 1 or 2 weeks meaning that the cookie will last for 1 or 2 weeks.

Thanks

-d

tags: & category: -