mway08 / owasp-esapi-java

Automatically exported from code.google.com/p/owasp-esapi-java
Other
0 stars 0 forks source link

SecurityWrapperResponse Forcefully Adds Secure Flag Breaking Non-SSL Sites #127

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
I was planning on recommending some ESAPI integration strategies to a
client and came across what appears to be a bug in the
SecurityWrapperResponse object. Looking at the “createCookieHeaer” method,
it forcefully adds the “Secure” flag without even checking the
configuration and or the “secure” boolean argument supplied to the method.
Won’t this break applications that are not running over SSL? This method is
called by addCookie when there are no errors or if the mode is sanitize. Is
there a way to optionally enable the Secure flag in this object that I am
missing?

Original issue reported on code.google.com by eshe...@gmail.com on 7 Jun 2010 at 1:26

GoogleCodeExporter commented 9 years ago
This has been fixed in ESAPI RC10. Issue #155. 

Original comment by augu...@gmail.com on 19 Oct 2010 at 12:58