Hi
I'm sorry I still do not understand.
Cookie header (as opposed to Set-Cookie) is not supposed to include
HttpOnly, this is why I'm curious, how does this Cookie header ends up
with HttpOnly ?
Thanks, Sergey
On 23/02/16 20:46, cc75005++ wrote:
Hi Sergey,
Thank you for your response.
In fact the httpOnly flag is done by my authentification rest service that
use NewCookie object.
So the question should be "how can I have access to a NewCookie object in my
ContainerRequestFilter ?
or maybe I've to use another class to filter my request ?
regards
--
View this message in context:
http://cxf.547215.n5.nabble.com/JAX-RS-CookieHeaderProvider-with-httpOnly-cookie-doesn-t-work-tp5766083p5766231.html
Sent from the cxf-user mailing list archive at Nabble.com.
