Are you using a browser to access that url? 'cause you mention ANT, but
ant is not a browser and will surely not show a dialog when accessing
the manager...
Mark Riggins a écrit :
Instead of a basic-authentication dialog box, I get the following error
message instead.
HTTP Status 401 -
I'm trying to access http://localhost/manager/html, which I believe is an
HTML interface into the Tomcat Manager.
Maybe it would be easier to edit build.xml and replace the "deploy" with a
simple copy. I can't get the Manager working.
Are you using a browser to
The message you see in browser, namely "HTTP Status 401 -" appear
probably because your browser for an unknown reason does not support
basic authentification or has it disabled (securities in browser that
prevent basic auth outside of ssl?). The text you see is normaly sent by
tomcat along
That's not it. I tried this site http://gemal.dk/browserspy/password.html
which has a basic authentication test built into it. It displayed and
worked properly in my browser. I am not using SSL. I don't have a
sniffer installed on XP [I'm more experienced with unix]
I don't want to put an
Mark Riggins wrote:
I don't want to put any move effort into it. I'll just avoid the Manager
instead if its that hard to set up.
The Manager works out of the box on a clean install. If it doesn't work for
you then something else is messed up in your configuration which is
probably going to b
Mark Riggins wrote:
>
>
> Instead of a basic-authentication dialog box, I get the following error
> message instead.
>
> HTTP Status 401 -
>
> type Status report
>
> message
>
>description This request requires HTTP authentication ().
>Apache Tomcat/
> From: wlievens [mailto:[EMAIL PROTECTED]
> Subject: Re: No Authentication Dialog appears for Tomcat Manager
>
> Mark Riggins wrote:
> > Instead of a basic-authentication dialog box, I get the
> > following error message instead.
> > HTTP Status 401 -
>
Unfortunately, I'm not sure, and I don't know how to recreate the problem.
Sorry.
Mark
David Smith-2 wrote:
>
> I'm just wondering if you got a 401 page, but a 200 status or something
> like that. Maybe one of your customizations did some filtering and/or
> proxying and changed the respons
I had this problem happen when I added custom error-page definitions in
the overall web.xml for the installation -- the error pages worked fine for my own
applications, but the fact that they were defined seemed to cause a problem for the
manager.
Soon as I commented-out all of them except the
I'm just wondering if you got a 401 page, but a 200 status or something
like that. Maybe one of your customizations did some filtering and/or
proxying and changed the response code. Seems like the most reasonable
cause of your problem.
--David
Mark Riggins wrote:
It turns out that Netbean
It turns out that Netbeans likes to use the Tomcat Manager, so I had to get
this working. Since others claimed that it worked "out of the box" I just
uninstalled everything [losing quite a bit of customization] and
did a clean vanilla install.
Now it works, but I have no idea what caused the pr
Hi,
I just experienced the same problem, found this thread via Google, and
figured I'd post my experience and solution.
Just like Mark's experience, I installed Tomcat and could not use the
manager app because the browser never presented me a dialog box for the
username and password. Sure e
Thanks!
Mark
David Simmons wrote:
>
> Hi,
>
> I just experienced the same problem, found this thread via Google, and
> figured I'd post my experience and solution.
>
> Just like Mark's experience, I installed Tomcat and could not use the
> manager app because the browser never presented me
13 matches
Mail list logo