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
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
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="..."
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.
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
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
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
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
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
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
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?
>
>
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
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
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
14 matches
Mail list logo
