Hi
Yes, you send a NewCookie but attempt to read it later on as Cookie.
You should use NewCookie.valueOf(newCookieValue) to recreate it.
Can you please use one of Cookie constructors to convert NewCookie to
Cookie ?
Or simply take the relevant value from this new cookie and send the name
Sorry, now I understand your question.. please find,I think, the bad code
that I use to create a new webclient to make the request :
Thanks for your time
--
View this message in context:
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
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
Hi
Can Cookie contain an attribute such as HttpOnly ? I'm not sure.
NewCookie has an isHttpOnly method - but not Cookie.
How is Set-Cookie processed on the client side ? By a browser or somehow
else ? I'm curious how HttpOnly is added to Cookie.
I guess if you have a Cookie with
Hello,
With Tomee 7.00-M1 (cxf 3.1.3) , If I send a request with an httponly cookie
on my rest service, I receive an IllegalArgumentException("Cookie is
malformed : " + c) when I call requestContext.getCookies().
Please find my container request filter implementation :
The CXF-6451
