Error in documentation

2011-12-22 Thread Peter Šály
Hi all,

I want to point on wrong setting example for tomcat manager in the
documentation:
http://tomcat.apache.org/tomcat-7.0-doc/manager-howto.html#Configuring_Manager_Application_Access
.



What should I put in tomcat-users.xml to access tomcat manager web app??

-- 
Best regards,
Peter Šály


Re: Error in documentation

2011-12-22 Thread Mark Thomas
On 22/12/2011 15:00, Peter Šály wrote:
> Hi all,
> 
> I want to point on wrong setting example for tomcat manager in the
> documentation:
> http://tomcat.apache.org/tomcat-7.0-doc/manager-howto.html#Configuring_Manager_Application_Access
> .
> 
> 

That example is correct.

> What should I put in tomcat-users.xml to access tomcat manager web app??

If you mean the HTML interface rather than the script interface, you
need the manager-gui role.

Mark

-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org



Re: Error in documentation

2011-12-22 Thread Pid
On 22/12/2011 15:00, Peter Šály wrote:
> Hi all,
> 
> I want to point on wrong setting example for tomcat manager in the
> documentation:
> http://tomcat.apache.org/tomcat-7.0-doc/manager-howto.html#Configuring_Manager_Application_Access

It is not wrong.  You just omitted the line beforehand:

"This file contains an XML  for each individual user, which
*might* look something like this:"  

(Starred as my emphasis.)

> 
> 
> What should I put in tomcat-users.xml to access tomcat manager web app??

It depends how you want to access it.

Assuming you are using Tomcat 7.0.x, if you want to use a web-browser
you need the "manager-gui" role defined and configured for a user.

Please not, it says below the line you reference:

"The HTML interface is protected against CSRF but the text and JMX
interfaces are not. To maintain the CSRF protection:

users with the manager-gui role should not be granted either the
manager-script or manager-jmx roles.
if the text or jmx interfaces are accessed through a browser (e.g. for
testing since these interfaces are intended for tools not humans) then
the browser must be closed afterwards to terminate the session."


p


-- 

[key:62590808]



signature.asc
Description: OpenPGP digital signature


Re: Error in documentation

2011-12-22 Thread Daniel Mikusa
On Thu, 2011-12-22 at 07:00 -0800, Peter Šály wrote:
> Hi all,
> 
> I want to point on wrong setting example for tomcat manager in the
> documentation:
> http://tomcat.apache.org/tomcat-7.0-doc/manager-howto.html#Configuring_Manager_Application_Access
> .
> 
> 

manager-script is the role to give a user when you want to allow
programmatic access to the manager application.  This is different than
the HTML GUI.

> What should I put in tomcat-users.xml to access tomcat manager web app??

To access the HTML GUI, assign the role manager-gui.

http://tomcat.apache.org/migration.html#Manager_application

  * manager-gui - allows access to the HTML GUI and the status pages
  * manager-script - allows access to the text interface and the
status pages
  * manager-jmx - allows access to the JMX proxy and the status
pages
  * manager-status - allows access to the status pages only

Dan



Re: Error in documentation

2011-12-22 Thread Peter Šály
Now I understand. Thank you.

2011/12/22 Daniel Mikusa 

> On Thu, 2011-12-22 at 07:00 -0800, Peter Šály wrote:
> > Hi all,
> >
> > I want to point on wrong setting example for tomcat manager in the
> > documentation:
> >
> http://tomcat.apache.org/tomcat-7.0-doc/manager-howto.html#Configuring_Manager_Application_Access
> > .
> >
> >  />
>
> manager-script is the role to give a user when you want to allow
> programmatic access to the manager application.  This is different than
> the HTML GUI.
>
> > What should I put in tomcat-users.xml to access tomcat manager web app??
>
> To access the HTML GUI, assign the role manager-gui.
>
> http://tomcat.apache.org/migration.html#Manager_application
>
>  * manager-gui - allows access to the HTML GUI and the status pages
>  * manager-script - allows access to the text interface and the
>status pages
>  * manager-jmx - allows access to the JMX proxy and the status
>pages
>  * manager-status - allows access to the status pages only
>
> Dan
>
>


Error in documentation, Tomcat 6

2010-09-27 Thread André Warnier

At the end of this page :

http://tomcat.apache.org/tomcat-6.0-doc/logging.html#log4j

there is this paragraph :

If you have multiple instances of Tomcat, each with a separate $CATALINA_HOME but a shared 
$CATALINA_BASE, then you can configure log4j on a per instance basis by replacing 
references to $CATALINA_HOME in the above instructions with $CATALINA_BASE. Note that you 
may need to create a $CATALINA_BASE/lib directory.



Is there not an inadvertent inversion in that paragraph ?
Should it not be

If you have multiple instances of Tomcat, each with a separate $CATALINA_BASE but a shared 
$CATALINA_HOME, then you can configure log4j on a per instance basis by replacing 
references to $CATALINA_HOME in the above instructions with $CATALINA_BASE. Note that you 
may need to create a $CATALINA_BASE/lib directory.



Note that this has been fixed in the equivalent Tomcat 7 page at
http://tomcat.apache.org/tomcat-7.0-doc/logging.html#log4j

At first sight, it also looks as if the 6.0 version of the whole page could be fixed by 
overwriting it (apart from the header part) with the 7.0 version, which also corrects 
another couple of mistakes.






-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org



Re: Error in documentation, Tomcat 6

2010-09-27 Thread Mark Thomas
On 27/09/2010 17:58, André Warnier wrote:
> At the end of this page :
> 
> http://tomcat.apache.org/tomcat-6.0-doc/logging.html#log4j

When looking at doc bugs I'd recommend working with the CI output which
will reflect and changes since the last release. The link above will
always be from the latest stable Tomcat 6 release so may not be 100% up
to date.

http://ci.apache.org/projects/tomcat/tomcat6/docs/logging.html

In this case the bug is still present.

> there is this paragraph :
> 
> If you have multiple instances of Tomcat, each with a separate
> $CATALINA_HOME but a shared $CATALINA_BASE, then you can configure log4j
> on a per instance basis by replacing references to $CATALINA_HOME in the
> above instructions with $CATALINA_BASE. Note that you may need to create
> a $CATALINA_BASE/lib directory.
> 
> Is there not an inadvertent inversion in that paragraph ?
Yep.

> Note that this has been fixed in the equivalent Tomcat 7 page at
> http://tomcat.apache.org/tomcat-7.0-doc/logging.html#log4j
> 
> At first sight, it also looks as if the 6.0 version of the whole page
> could be fixed by overwriting it (apart from the header part) with the
> 7.0 version, which also corrects another couple of mistakes.

Care to provide a patch? Offer of help with building etc. still stands
if required.

Mark

-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org