javascript - When is it appropriate to have non-HttpOnly cookies on your domain? -
i have read owasp information , range of articles including jeff atwood's protecting cookies article , still feel need understand httponly cookies better.
this came because needed add google adword tracking code site. javascript needed set , read cookie on website's domain , assumed issue. website .net application httponlycookies="true" in web.config, assumed best approach replace javascript , write cookie backend ensure generated cookie httponly. read cookie in server-side too.
i understand setting httponly of cookie property largely prevents cookie being read , manipulated client. don't understand is:
- given example above, there have been problem me using javascript implementation?
- would still have been ok write cookie using javascript (but still read using server-side)? i'm thinking not cookie not httponly cookie
- if have done right thing (moving server-side implementation), why google analytic cookies implemented non-httponly cookies? surely pose security issue too?
so title says, guess i'm asking - when (if ever) appropriate have non-httponly cookies on domain?
so more straightforward assumed. according comments left @mah above, flagging cookie httponly redundant when cookie contains non-sensitive information.
Comments
Post a Comment