Hi, anyone come across the situation where a webapp is coded to use FORM
based authentication but behaves as if it was using BASIC authentication i.e
OS username/password dialog pops up instead of the redirection to the login
form. The web.xml is very basic so i'm almost thinking its something in
same applies on Firefox though, there may well be issues in IE as always but
i'm not convinced this is the core problem here.
Gregor Schneider wrote:
>
> Bill,
>
> On Thu, Dec 11, 2008 at 4:15 AM, Bill Barker <[EMAIL PROTECTED]> wrote:
>>
>> The article is referring to the fact that Tomcat ad
The problem however is that i'm using a remote shared host. Whilst this gives
me quite a lot of configuration potential i doubt it would allow me to setup
Apache and adaptors etc. In a 'real production environment' this would very
much be a preferred choice.
awarnier wrote:
>
> As a heretic pos
I agree that i dont think the 'in memory' Tomcat solutions is what i'm
currently after, its very much a Tomcat 'heading stamp' issue i think.
Interesting point you raise though regarding pushing the statics to an
external server. Not ideal from a deployment perspective but that would
certainly sol
Thanks Chuck for that. Perhaps my use of words was a little misleading. I
guess what i was trying to say was that the response returned by Tomcat i.e
expiry date etc was not conductive to caching for clients. In terms of
headers, i dont want to cache 'pages as the data is very transient. What i
di
