As I said, HTTP doesn't have the idea of a session. To do what you want,
you'd have to implement your own authentication layer rather than
relying on the container. Hmm, come to think of it, form based container
managed security may work close to the way you want. You might be able
to bend that
Hello laurie,
You are right..
Heres what i got from apache website..[see below]
The confusion was because for some reason i was not able to see authorisation
header[cached user credentials for subsequent requests] being sent from my
browser client..
On a different note,is there an
Hello Laurie,
Thanks for your response..
Iam purposefully not sending authentication header for second request as i
want to maintain "authenticated session" with the server till the client closes
the connection..
>>Sending a session cookie has no effect on HTTP authentication.
Than hows
Prashanth.S wrote:
Hello All,
I have got a simple question on BASIC authentication on webresources using
Tomcat.
I had set up this BASIC authentication on tomcat and tomcat[because of my misconfiguration] seems to authenticate user every time they accesses resource though the client
4 matches
Mail list logo