>I have implemented the mod_jk (1.2) request logging I proposed 
>a few weeks
>ago.  Its up and running.
>
>/*
> * JkRequestLogFormat Directive Handling
> *
> * JkRequestLogFormat format string
> *
> * %b - Bytes sent, excluding HTTP headers. In CLF format
> * %B - Bytes sent, excluding HTTP headers.
> * %H - The request protocol               
> * %m - The request method                 
> * %p - The canonical Port of the server serving the request
> * %q - The query string (prepended with a ? if a query string exists,
> *      otherwise an empty string)                                    
> * %r - First line of request                                         
> * %s - request HTTP status code  
> * %T - Requset duration, elapsed time to handle request in 
>seconds '.' micro seconds
> * %U - The URL path requested, not including any query 
>string.                      
> * %v - The canonical ServerName of the server serving the 
>request.                  
> * %V - The server name according to the UseCanonicalName setting. 
> * %w - Tomcat worker name                                         
> */

Excellent

>Another log level of "request" was added also.  If log level 
>is <= request
>and JkRequestLogFormat is configured, requests will be logged.

If JkLogLevel <= REQUEST ?

Why not use instead JkLogLevel INFO + REQUEST to explicitly 
explain we want request logged

>This is only implemented for Apache 1.3 and I cloned alot of 
>code from the
>Apache httpd logging module to implement this.

Could be factorized to be used later by Apache 1.3/2.0 for mod_jk 1.2.
And of course jk2 will use it in a similar fashion (must be easier with
new architecture)

>---------------------------------------------------------------
>--------------------
>
>I also added a new config directive called JkAutoAlias, again this is
>only implemented for Apache 1.3.
>
>JkAutoAlias {webapp directory}
>
>JkAutoAlias is used when you want to map static files in a webapp
>context directory into the Apache virtual host document space so 
>it can serve the static pages instead of Tomcat.
>
>This works automatically for an context in the configured 
>webapp directory
>which has a context directory. And is a great deal easier than 
>configuring
>an Apache Alias for each individual webapp context directory.

So you'll have :

JkAutoAlias examples
JkAutoAlias admin
JkAutoAlias webappxxxx


>---------------------------------------------------------------
>---------------------
>
>I made one other minor change to how JkMount works which 
>applies to all web servers.
>
>I added the ability to configure a * for the context 
>directory, then match on the
>remaining path.
>
>Here is an example:
>
>JkMount /*/servlet/ ajp13

Great

>The above would forward all requests where the second path 
>component is named "servlet"
>to Tomcat.  This also makes it easier to configure a virtual 
>host to handle multiple
>web application contexts without having tho change the Apache config.
>
>
>I haven't contributed code  to jakarta-tomcat-connectors, but 
>if everyone is OK with
>this I can commit the code.

Could you send us the patches for study, but it allready appears
to be great addition

--
To unsubscribe, e-mail:   <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>

Reply via email to