Thank you both. Removing the element quickly solved
the problem for me. So far, I have not run into any MSIE problems with
this solution, hopefully my luck will continue. (By default, users will
be given https:// links anyway, the redirection is only for those who
might accidentally enter v
Yeah, you need to delete the entire ...
to allow everyone. However, for MSIE, you may still get problems due to the
restricted caching headers that Tomat adds.
"Filip Hanik - Dev Lists" <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]
> *
>
> the "*" means all the roles that you h
*
the "*" means all the roles that you have defined in web.xml, since you
haven't defined any roles in web.xml, there is nothing to authenticate,
hence its gonna deny the request
Filip
Glen Mazza wrote:
Hello,
I have developed a simple web application running on Tomcat that asks
for a
Hello,
I have developed a simple web application running on Tomcat that asks
for a database username and password and then returns a report in PDF.
I'm *not* using any of Tomcat's security features for this--no roles for
example.
In testing it has been running fine on HTTP, but I would like
