Martin, You really are great. Thank you for your response. It's incredible you take time to answer even when the questions was not much wicket beared.
I hope I can return the community as much as you gave us. Thank you again. El lun, 29-04-2013 a las 07:57 +0200, Martin Grigorov escribió: > Hi, > > See http://www.w3.org/Protocols/rfc2616/rfc2616-sec14.html, p. 14.8. > The "Authorization" header is a _request_ header. I.e. the user agent > should set it. Wicket can set _response_ headers. An exception is Ajax > request where Wicketcan set request headers. > > Your use case sounds like normal session tracking. Once authenticated you > bind a session. This way the servlet container will use either JSESSIONID > cookie or jsessionid request path parameter. > > > On Mon, Apr 29, 2013 at 3:23 AM, Gonzalo Aguilar Delgado < > [email protected]> wrote: > > > Hello, > > > > I'm using AuthenticatedWebApplication class to manage my login and > > roles. While it works well I want wicket to set the "Authorization" http > > header each time it does a request. > > > > I don't really know if this makes sense. > > > > The application is currently working in this context > > > > http://localhost:8080/lead-services-war/ > > > > If I login wicket should set the "Authorization" header in http. > > > > > > I have some services running in > > http://localhost:8080/lead-services-war/services and I need to use the > > same authorization made by wicket in this services. Do you know how to > > propagate this authorization? > > > > Thank you a lot in advance. > > > > Best regards, > > > > >
