Hi Martin,
Many thanks for your explanation and tip!
Regards,
Ian
Martin Grigorov-4 wrote
Hi,
Headers are not cookies.
By setting a header in the response you should not expect that it will
come in the next request.
A request header is set by the client (the browser in this case).
Hi Martin,
COOKIES
---
I'm fine for this. My cookie code actually works. (But if the user's browser
disables cookies, then I want to use HTTP headers to be able to say The
user is on his/her second page, and still no cookie, so cookies are
definitely disabled (I cannot tell this on the first
Hi,
Headers are not cookies.
By setting a header in the response you should not expect that it will
come in the next request.
A request header is set by the client (the browser in this case). You
can use UrlConnection or Apache HttpClient to set header request
which will be available thru
Hello Jeff,
Thanks for the tip. I have tried to detect my header in the HTTP response
headers using, in my web application class:
@Override
protected WebResponse MyWebApplicationnewWebResponse(final WebRequest
webRequest,
final HttpServletResponse httpServletResponse)
{
Hi Ian,
If you add/set a header in the HttpServletResponse (even thru Wicket's
WebResponse) then it will be written to the browser. You can verify
that by investigating the request in Firebug's Net panel.
If you want to send a cookie you should either use #addCookie() or
The header won't appear in the browser's page source but will be in the http
response header.
Sent from my iPhone
On Feb 17, 2012, at 12:01 PM, Ian Marshall ianmarshall...@gmail.com wrote:
I am having trouble with JSessionIDs in my URLs (my post at
