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
Original issue reported on code.google.com by
eshe...@gmail.com
on 7 Jun 2010 at 1:26