Hi Martin,

Many thanks for your explanation and tip!



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). You
> can use UrlConnection or Apache HttpClient to set header request
> which will be available thru WebRequest.getHeader().
> Cookies work as you want - set it once in the response and then it
> will travel around in the next requests/responses until expire.

View this message in context: 
Sent from the Users forum mailing list archive at Nabble.com.

To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org

Reply via email to