might be trying to send headers,
unfortunately I am not in the same location as the server so I will have
to check this out tomorrow.
I'll keep you posted,
~Matt
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Matthew,
On 6/30/2010 8:20 PM, Matthew Mauriello wrote:
The behavior seems
-
Hash: SHA1
Matthew,
On 6/30/2010 12:07 AM, Matthew Mauriello wrote:
I have two directories in 'webapps' other than ROOT. ROOT redirects
users
to webappA. WebappA does not use tomcat's basic authentication but if
you
log into the application there are links inside it that sends the user
, Matthew Mauriello wrote:
The behavior seems rather strange to me in fact, I've seen other
websites
run on what looks to be BASIC Authentication without popping these
browser
messages when leaving secured sections.
Most websites use HTTP AUTH consistently, at least for a particular URL
PGP SIGNED MESSAGE-
Hash: SHA1
Matthew,
On 6/30/2010 8:20 PM, Matthew Mauriello wrote:
The behavior seems rather strange to me in fact, I've seen other
websites
run on what looks to be BASIC Authentication without popping these
browser
messages when leaving secured sections.
Most
of the very few
users on the website.
Hope this clears things up.
Thanks,
~Matt
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Matt,
On 6/29/2010 5:57 PM, Matthew Mauriello wrote:
I am having a minor problem related to Tomcat's BASIC Authentication
setup.
A user access my custom web
