Affects Version/s: 5.0.15
Fix Version/s: 5.0.16
A lot op applications are vulerable to a sniffing 'attack' even though
SSL is used. The vulnerability is caused by allowing the cookie to be
sent over http (the cookie is not a secure cookie)
My application always uses HTTPS because I have set
MetaDataConstants.SECURE_PAGE to true. The cookie however is not a
secure cookie because Tapestry does set the Cookie#setSecure attribute.
What I would like is that Tapestry does sets Cookie#setSecure when
SECURE_PAGE is true.
It seems that tomcat does set the secure setting but not with Jetty.