Re: Apache SSI breaks with tomcat-connectors-1.2.43 or newer

2020-01-07 Thread Mark Thomas
On 07/01/2020 20:22, Ezsra McDonald wrote:
> Mark,
> 
> Has there been a decision on when a new release with the fix will go out?

It hasn't been forgotten. It is around the middle of my fairly long TODO
list.

I'd like to say I should get to it this month but between the stuff that
is already above it on the TODO list and what might turn up in the next
few weeks I can't be at all sure I'll get to it by the end of the month.

Mark


> 
> On Fri, Oct 4, 2019 at 10:50 AM Ezsra McDonald 
> wrote:
> 
>> The SVN Build works for us! Thanks Mark.
>>
>> When do you think the official release will be ready?
>>
>> --Ez
>>
>> On Wed, Oct 2, 2019 at 10:02 AM Mark Thomas  wrote:
>>
>>> On 02/10/2019 15:39, Mark Thomas wrote:
 On 02/10/2019 14:51, Mark Thomas wrote:
>>>
>>>
>>> 
>>>
 There is a work-around. Use virtual="..." in the SSI includes.

 Meanwhile, I am working on a fix for mod_jk.
>>>
>>> Done. If you want to test it out you'll have to build from svn.
>>> Meanwhile, I'll start thinking about a mod_jk release. We haven't had
>>> one for about a year and this bug fix seems like a good reason to have
>>> one.
>>>
>>> Mark
>>>
>>> -
>>> To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
>>> For additional commands, e-mail: users-h...@tomcat.apache.org
>>>
>>>
> 


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



Re: Apache SSI breaks with tomcat-connectors-1.2.43 or newer

2020-01-07 Thread Ezsra McDonald
Mark,

Has there been a decision on when a new release with the fix will go out?

On Fri, Oct 4, 2019 at 10:50 AM Ezsra McDonald 
wrote:

> The SVN Build works for us! Thanks Mark.
>
> When do you think the official release will be ready?
>
> --Ez
>
> On Wed, Oct 2, 2019 at 10:02 AM Mark Thomas  wrote:
>
>> On 02/10/2019 15:39, Mark Thomas wrote:
>> > On 02/10/2019 14:51, Mark Thomas wrote:
>>
>>
>> 
>>
>> > There is a work-around. Use virtual="..." in the SSI includes.
>> >
>> > Meanwhile, I am working on a fix for mod_jk.
>>
>> Done. If you want to test it out you'll have to build from svn.
>> Meanwhile, I'll start thinking about a mod_jk release. We haven't had
>> one for about a year and this bug fix seems like a good reason to have
>> one.
>>
>> Mark
>>
>> -
>> To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
>> For additional commands, e-mail: users-h...@tomcat.apache.org
>>
>>


Re: Apache SSI breaks with tomcat-connectors-1.2.43 or newer

2019-10-04 Thread Ezsra McDonald
The SVN Build works for us! Thanks Mark.

When do you think the official release will be ready?

--Ez

On Wed, Oct 2, 2019 at 10:02 AM Mark Thomas  wrote:

> On 02/10/2019 15:39, Mark Thomas wrote:
> > On 02/10/2019 14:51, Mark Thomas wrote:
>
>
> 
>
> > There is a work-around. Use virtual="..." in the SSI includes.
> >
> > Meanwhile, I am working on a fix for mod_jk.
>
> Done. If you want to test it out you'll have to build from svn.
> Meanwhile, I'll start thinking about a mod_jk release. We haven't had
> one for about a year and this bug fix seems like a good reason to have one.
>
> Mark
>
> -
> To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
> For additional commands, e-mail: users-h...@tomcat.apache.org
>
>


Re: Apache SSI breaks with tomcat-connectors-1.2.43 or newer

2019-10-03 Thread Ezsra McDonald
Mark,

Thanks for taking a look.

I will try the SVN build and let you know.

--Ez

On Wed, Oct 2, 2019 at 10:02 AM Mark Thomas  wrote:

> On 02/10/2019 15:39, Mark Thomas wrote:
> > On 02/10/2019 14:51, Mark Thomas wrote:
>
>
> 
>
> > There is a work-around. Use virtual="..." in the SSI includes.
> >
> > Meanwhile, I am working on a fix for mod_jk.
>
> Done. If you want to test it out you'll have to build from svn.
> Meanwhile, I'll start thinking about a mod_jk release. We haven't had
> one for about a year and this bug fix seems like a good reason to have one.
>
> Mark
>
> -
> To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
> For additional commands, e-mail: users-h...@tomcat.apache.org
>
>


Re: Apache SSI breaks with tomcat-connectors-1.2.43 or newer

2019-10-02 Thread Mark Thomas
On 02/10/2019 15:39, Mark Thomas wrote:
> On 02/10/2019 14:51, Mark Thomas wrote:




> There is a work-around. Use virtual="..." in the SSI includes.
> 
> Meanwhile, I am working on a fix for mod_jk.

Done. If you want to test it out you'll have to build from svn.
Meanwhile, I'll start thinking about a mod_jk release. We haven't had
one for about a year and this bug fix seems like a good reason to have one.

Mark

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



Re: Apache SSI breaks with tomcat-connectors-1.2.43 or newer

2019-10-02 Thread Mark Thomas
On 02/10/2019 14:51, Mark Thomas wrote:
> On 30/09/2019 20:33, Rainer Jung wrote:
>> Thanks, eactly what we need.
> 
> +1. I can reproduce this.
> 
>> I will look into it, but it might take two
>> or three days. Anyone who can do it more quickly is welcome. I suspect
>> these log lines point to the root cause:
>>
>>> [Mon Sep 30 15:04:03 2019][3906:140148297873536] [debug]
>>> jk_servlet_normalize::jk_util.c (2184): URI on entering
>>> jk_servlet_normalize: []
>>> [Mon Sep 30 15:04:03 2019][3906:140148297873536] [emerg]
>>> jk_servlet_normalize::jk_util.c (2188): [] does not start with '/'.
>>> [Mon Sep 30 15:04:03 2019][3906:140148297873536] [debug]
> 
> Also agreed.
> 
>> but we'll need to investigate whether it can be fixed by configuration
>> or needs a code change. Our configs are pretty flexible but we need to
>> understand a bit better how we can let mod_jk keep out of the SSI
>> handling of the internal requests.
>>
>> As far as I have understood, you do not actually want these SSI requests
>> to be forwarded via mod_jk/AJP and instead want all of them being
>> handled directly by Apache?
> 
> That is my understanding as well.

I've figured out what is going on here.

The SSI includes are using file="..." so they are entirely file system
based. Therefore, the URI in the sub-request is set to "". When this is
passed to mod_jk, it tries to normalise it, complains because it does
not start with "/" and then returns an error. This prevents the
processing of the sub-request. mod_jk returns an error since
normalisation errors typically mean path traversal attempts and other
similar client misbehaviour.

There is a work-around. Use virtual="..." in the SSI includes.

Meanwhile, I am working on a fix for mod_jk.

Mark

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



Re: Apache SSI breaks with tomcat-connectors-1.2.43 or newer

2019-10-02 Thread Mark Thomas
On 30/09/2019 20:33, Rainer Jung wrote:
> Thanks, eactly what we need.

+1. I can reproduce this.

> I will look into it, but it might take two
> or three days. Anyone who can do it more quickly is welcome. I suspect
> these log lines point to the root cause:
> 
>> [Mon Sep 30 15:04:03 2019][3906:140148297873536] [debug]
>> jk_servlet_normalize::jk_util.c (2184): URI on entering
>> jk_servlet_normalize: []
>> [Mon Sep 30 15:04:03 2019][3906:140148297873536] [emerg]
>> jk_servlet_normalize::jk_util.c (2188): [] does not start with '/'.
>> [Mon Sep 30 15:04:03 2019][3906:140148297873536] [debug]

Also agreed.

> but we'll need to investigate whether it can be fixed by configuration
> or needs a code change. Our configs are pretty flexible but we need to
> understand a bit better how we can let mod_jk keep out of the SSI
> handling of the internal requests.
> 
> As far as I have understood, you do not actually want these SSI requests
> to be forwarded via mod_jk/AJP and instead want all of them being
> handled directly by Apache?

That is my understanding as well.

Mark

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



Re: Apache SSI breaks with tomcat-connectors-1.2.43 or newer

2019-10-02 Thread glal
Hi all,

I have almost the same issue with SSI provided by AEM Sling Dynamic Include.
Page shows error message instead of html block:
*[an error occurred while processing this directive]*

Dispatcher error log file has lines like: 
/unable to include
"/content/my-site/st-marys/_jcr_content/content/location_result.nocache.html"
in parsed file /data/dispatcher/cache/default/content/my-site/st-marys.html,
subrequest setup returned 301/

I would be happy if someone has any thoughts. Thanks.



--
Sent from: http://tomcat.10.x6.nabble.com/Tomcat-User-f1968778.html

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



Re: Apache SSI breaks with tomcat-connectors-1.2.43 or newer

2019-09-30 Thread Rainer Jung
Thanks, eactly what we need. I will look into it, but it might take two 
or three days. Anyone who can do it more quickly is welcome. I suspect 
these log lines point to the root cause:


> [Mon Sep 30 15:04:03 2019][3906:140148297873536] [debug]
> jk_servlet_normalize::jk_util.c (2184): URI on entering
> jk_servlet_normalize: []
> [Mon Sep 30 15:04:03 2019][3906:140148297873536] [emerg]
> jk_servlet_normalize::jk_util.c (2188): [] does not start with '/'.
> [Mon Sep 30 15:04:03 2019][3906:140148297873536] [debug]

but we'll need to investigate whether it can be fixed by configuration 
or needs a code change. Our configs are pretty flexible but we need to 
understand a bit better how we can let mod_jk keep out of the SSI 
handling of the internal requests.


As far as I have understoff, you do not actually want these SSI requests 
to be forwarded via mod_jk/AJP and instead want all of them being 
handled directly by Apache?


regards,

Rainer

Am 30.09.2019 um 17:17 schrieb Ezsra McDonald:


Apologies as this is a long e-mail. I tried to include all the 
information to help troubleshoot the issue.


I have a lab setup with  a vagrant box to test.: CentOS Linux release 
7.7.1908 (Core)


httpd-2.4.6-90.el7
tomcat-connectors-1.2.44-src

The only changes I made to the config from default install are as follows

#*
FILE: /etc/httpd/conf/httpd.conf

#test-ssi

    Options +Includes
    AddHandler server-parsed .shtml


#*
FILE: /etc/httpd/conf/workers.properties

This file is currently blank.

#*
FILE: /etc/httpd/conf.d/mod_jk.conf

# Load mod_jk module
# Specify the filename of the mod_jk lib
#LoadModule jk_module modules/mod_jk.so



     # Where to find workers.properties
     JkWorkersFile conf/workers.properties

     # Where to put jk logs
     JkLogFile logs/mod_jk.log

     # Set the jk log level [debug/error/info]
     #JkLogLevel info
     JkLogLevel trace

     # Select the log format
     JkLogStampFormat  "[%a %b %d %H:%M:%S %Y]"

     # JkOptions indicates to send SSK KEY SIZE
     JkOptions +ForwardKeySize +ForwardURICompat -ForwardDirectories

     # JkRequestLogFormat
     JkRequestLogFormat "%w %V %T"

     # Mount your applications
     # The default setting only sends Java application data to mod_jk.
     # Use the commented-out line to send all URLs through mod_jk.
     # JkMount /* loadbalancer
     # JkMount /application/* loadbalancer
     #JkMountFile conf.d/uriworkermap.properties

     # Add shared memory.
     # This directive is present with 1.2.10 and
     # later versions of mod_jk, and is needed for
     # for load balancing to work properly
     JkShmFile logs/jk.shm

     # Should mod_jk send SSL information (default is On)
     JkExtractSSL On
     # What is the indicator for SSL (default is HTTPS)
     JkHTTPSIndicator HTTPS
     # What is the indicator for SSL session (default is SSL_SESSION_ID)
     JkSESSIONIndicator SSL_SESSION_ID
     # What is the indicator for client SSL cipher suit (default is 
SSL_CIPHER)

     JkCIPHERIndicator SSL_CIPHER
     # What is the indicator for the client SSL certificated? (default 
is SSL_CLIENT_CERT)

     JkCERTSIndicator SSL_CLIENT_CERT

     # Add jkstatus for managing runtime data
     
         Order deny,allow
         Deny from all
         Allow from localhost 192.168.19.54 192.168.19.52
     



#*
FILE: /etc/httpd/conf.modules.d/02-mod_jk.conf

# This file configures the mod_jk modules:
LoadModule jk_module modules/mod_jk.so

#*
SSI Structure modeled after a previously working customer site.

[vagrant@WEBSRV test-ssi]$ tree /var/www/html/test-ssi
/var/www/html/test-ssi
├── includes
│   ├── footer.html
│   └── header.html
└── index.shtml

#*
FILE: /var/www/html/test-ssi/index.shtml


   
       SSI Test stuff
   
   
       
         
       
         
       
   


#*
When I load index.shtml in the browser I get the following page:

[an error occurred while processing this directive]
[an error occurred while processing this directive]

#*
error_log

[Mon Sep 30 15:04:03.634861 2019] [include:error] [pid 3906] [client 
10.211.55.42:37042 ] unable to include 
"includes/header.html" in parsed file 
/var/www/html/test-ssi/index.shtml, subrequest setup returned 404
[Mon Sep 30 15:04:03.634907 2019] [include:error] [pid 3906] [client 
10.211.55.42:37042 ] unable to include 
"includes/footer.html" in parsed file 
/var/www/html/test-ssi/index.shtml, subrequest setup returned 404


#*
If I reconfigure the SSI structure as follows the SSI works:


Re: Apache SSI breaks with tomcat-connectors-1.2.43 or newer

2019-09-30 Thread Ezsra McDonald
Apologies as this is a long e-mail. I tried to include all the information
to help troubleshoot the issue.

I have a lab setup with  a vagrant box to test.: CentOS Linux release
7.7.1908 (Core)

httpd-2.4.6-90.el7
tomcat-connectors-1.2.44-src

The only changes I made to the config from default install are as follows

#*
FILE: /etc/httpd/conf/httpd.conf

#test-ssi

   Options +Includes
   AddHandler server-parsed .shtml


#*
FILE: /etc/httpd/conf/workers.properties

This file is currently blank.

#*
FILE: /etc/httpd/conf.d/mod_jk.conf

# Load mod_jk module
# Specify the filename of the mod_jk lib
#LoadModule jk_module modules/mod_jk.so



# Where to find workers.properties
JkWorkersFile conf/workers.properties

# Where to put jk logs
JkLogFile logs/mod_jk.log

# Set the jk log level [debug/error/info]
#JkLogLevel info
JkLogLevel trace

# Select the log format
JkLogStampFormat  "[%a %b %d %H:%M:%S %Y]"

# JkOptions indicates to send SSK KEY SIZE
JkOptions +ForwardKeySize +ForwardURICompat -ForwardDirectories

# JkRequestLogFormat
JkRequestLogFormat "%w %V %T"

# Mount your applications
# The default setting only sends Java application data to mod_jk.
# Use the commented-out line to send all URLs through mod_jk.
# JkMount /* loadbalancer
# JkMount /application/* loadbalancer
#JkMountFile conf.d/uriworkermap.properties

# Add shared memory.
# This directive is present with 1.2.10 and
# later versions of mod_jk, and is needed for
# for load balancing to work properly
JkShmFile logs/jk.shm

# Should mod_jk send SSL information (default is On)
JkExtractSSL On
# What is the indicator for SSL (default is HTTPS)
JkHTTPSIndicator HTTPS
# What is the indicator for SSL session (default is SSL_SESSION_ID)
JkSESSIONIndicator SSL_SESSION_ID
# What is the indicator for client SSL cipher suit (default is
SSL_CIPHER)
JkCIPHERIndicator SSL_CIPHER
# What is the indicator for the client SSL certificated? (default is
SSL_CLIENT_CERT)
JkCERTSIndicator SSL_CLIENT_CERT

# Add jkstatus for managing runtime data

Order deny,allow
Deny from all
Allow from localhost 192.168.19.54 192.168.19.52




#*
FILE: /etc/httpd/conf.modules.d/02-mod_jk.conf

# This file configures the mod_jk modules:
LoadModule jk_module modules/mod_jk.so

#*
SSI Structure modeled after a previously working customer site.

[vagrant@WEBSRV test-ssi]$ tree /var/www/html/test-ssi
/var/www/html/test-ssi
├── includes
│   ├── footer.html
│   └── header.html
└── index.shtml

#*
FILE: /var/www/html/test-ssi/index.shtml


  
  SSI Test stuff
  
  
  

  

  
  


#*
When I load index.shtml in the browser I get the following page:

[an error occurred while processing this directive]
[an error occurred while processing this directive]

#*
error_log

[Mon Sep 30 15:04:03.634861 2019] [include:error] [pid 3906] [client
10.211.55.42:37042] unable to include "includes/header.html" in parsed file
/var/www/html/test-ssi/index.shtml, subrequest setup returned 404
[Mon Sep 30 15:04:03.634907 2019] [include:error] [pid 3906] [client
10.211.55.42:37042] unable to include "includes/footer.html" in parsed file
/var/www/html/test-ssi/index.shtml, subrequest setup returned 404

#*
If I reconfigure the SSI structure as follows the SSI works:

/var/www/html/test-ssi
├── footer.html
├── header.html
└── index.shtml

FILE: /var/www/html/test-ssi/index.shtml


  
  SSI Test stuff
  
  
  

  

  
  


It seems like mod_include can not find resources in sub directories


#*
FILE: /var/log/httpd/mod_jk.log. (257 lines. happy reading)

[Mon Sep 30 15:01:43 2019][3905:140148297873536] [debug]
jk_set_time_fmt::jk_util.c (487): Pre-processed log time stamp format is
'[%a %b %d %H:%M:%S %Y]'
[Mon Sep 30 15:01:43 2019][3905:140148297873536] [debug]
dump_options::mod_jk.c (665): JkOption 'ForwardURICompat' set in server
'127.0.0.1'
[Mon Sep 30 15:01:43 2019][3905:140148297873536] [debug]
dump_options::mod_jk.c (673): JkOption 'ForwardURIEscaped' set in server
'127.0.0.1'
[Mon Sep 30 15:01:43 2019][3905:140148297873536] [debug]
dump_options::mod_jk.c (697): JkOption 'ForwardKeySize' set in server
'127.0.0.1' (default)
[Mon Sep 30 15:01:43 2019][3905:140148297873536] [trace]
uri_worker_map_alloc::jk_uri_worker_map.c (216): enter
[Mon Sep 30 15:01:43 2019][3905:140148297873536] [trace]

Re: Apache SSI breaks with tomcat-connectors-1.2.43 or newer

2019-09-25 Thread Ezsra McDonald
Thank you Mark,



I never saw Rainer's response. I just found it in my SPAM folder. I will
look it over.


-Ez


On Wed, Sep 25, 2019 at 10:26 AM Mark Thomas  wrote:

> On 25/09/2019 16:13, Ezsra McDonald wrote:
> > Hello,
> > Does anyone have any suggestions? Am I missing something obvious?
>
> See Rainer's response the day after your post.
>
> Given the issue appeared between 1.2.42 and 1.2.43, it might be related
> to the fix for CVE-2019-1175 but we need the information Rainer asked
> for to identify the root cause.
>
> Mark
>
>
> >
> > --Ez
> >
> > On Tue, Sep 17, 2019 at 10:44 AM Ezsra McDonald <
> ezsra.mcdon...@gmail.com>
> > wrote:
> >
> >> Hello,
> >>
> >> Environment:
> >> OS: CentOS 7
> >> Apache: Apache/2.4.6 (CentOS)
> >> Working Connector: tomcat-connectors-1.2.42
> >>
> >> When we installed the latest version of the connector, 1.2.46 at this
> >> time, some of our customer Server Side Includes stopped working. SSIs
> using
> >> the  directives produce the following
> >> error in the log files:
> >>
> >> unable to include "layout/includes/headernav.html" in parsed file
> >> /var/www/html/horses/index.shtml, subrequest setup returned 400,
> referer:
> >> http://10.211.55.44/horses/
> >>
> >> When we roll back to tomcat-connectors-1.2.42 the SSI works.
> >>
> >> We do not know why tomcat-connectors impact mod_include.
> >>
> >> Any assistance would be appreciated.
> >>
> >> -Ez
> >>
> >
>
>
> -
> To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
> For additional commands, e-mail: users-h...@tomcat.apache.org
>
>


Re: Apache SSI breaks with tomcat-connectors-1.2.43 or newer

2019-09-25 Thread Mark Thomas
On 25/09/2019 16:13, Ezsra McDonald wrote:
> Hello,
> Does anyone have any suggestions? Am I missing something obvious?

See Rainer's response the day after your post.

Given the issue appeared between 1.2.42 and 1.2.43, it might be related
to the fix for CVE-2019-1175 but we need the information Rainer asked
for to identify the root cause.

Mark


> 
> --Ez
> 
> On Tue, Sep 17, 2019 at 10:44 AM Ezsra McDonald 
> wrote:
> 
>> Hello,
>>
>> Environment:
>> OS: CentOS 7
>> Apache: Apache/2.4.6 (CentOS)
>> Working Connector: tomcat-connectors-1.2.42
>>
>> When we installed the latest version of the connector, 1.2.46 at this
>> time, some of our customer Server Side Includes stopped working. SSIs using
>> the  directives produce the following
>> error in the log files:
>>
>> unable to include "layout/includes/headernav.html" in parsed file
>> /var/www/html/horses/index.shtml, subrequest setup returned 400, referer:
>> http://10.211.55.44/horses/
>>
>> When we roll back to tomcat-connectors-1.2.42 the SSI works.
>>
>> We do not know why tomcat-connectors impact mod_include.
>>
>> Any assistance would be appreciated.
>>
>> -Ez
>>
> 


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



Re: Apache SSI breaks with tomcat-connectors-1.2.43 or newer

2019-09-25 Thread Ezsra McDonald
Hello,
Does anyone have any suggestions? Am I missing something obvious?

--Ez

On Tue, Sep 17, 2019 at 10:44 AM Ezsra McDonald 
wrote:

> Hello,
>
> Environment:
> OS: CentOS 7
> Apache: Apache/2.4.6 (CentOS)
> Working Connector: tomcat-connectors-1.2.42
>
> When we installed the latest version of the connector, 1.2.46 at this
> time, some of our customer Server Side Includes stopped working. SSIs using
> the  directives produce the following
> error in the log files:
>
> unable to include "layout/includes/headernav.html" in parsed file
> /var/www/html/horses/index.shtml, subrequest setup returned 400, referer:
> http://10.211.55.44/horses/
>
> When we roll back to tomcat-connectors-1.2.42 the SSI works.
>
> We do not know why tomcat-connectors impact mod_include.
>
> Any assistance would be appreciated.
>
> -Ez
>


Re: Apache SSI breaks with tomcat-connectors-1.2.43 or newer

2019-09-18 Thread Rainer Jung

Am 17.09.2019 um 17:44 schrieb Ezsra McDonald:

Hello,

Environment:
OS: CentOS 7
Apache: Apache/2.4.6 (CentOS)
Working Connector: tomcat-connectors-1.2.42

When we installed the latest version of the connector, 1.2.46 at this time,
some of our customer Server Side Includes stopped working. SSIs using
the  directives produce the following error in the log
files:

unable to include "layout/includes/headernav.html" in parsed file
/var/www/html/horses/index.shtml, subrequest setup returned 400, referer:
http://10.211.55.44/horses/

When we roll back to tomcat-connectors-1.2.42 the SSI works.

We do not know why tomcat-connectors impact mod_include.

Any assistance would be appreciated.


It seems you can easily reproduce. Can you set JkLogLevel to trace and 
run one request that shows the failure? Then provide the resulting 
mod_jk log file plus your mod_jk configuration (all Jk... diractives 
plus workers.properties plus uriworkermap.properties or similar if in use).


Thanks and regards,

Rainer


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