On Sun, Jun 14, 2015 at 2:43 AM, Jeff Trawick wrote:
> On Sat, Jun 13, 2015 at 8:25 PM, Yann Ylavic wrote:
>>
>> On Sun, Jun 14, 2015 at 2:18 AM, Jeff Trawick wrote:
>> > On Sat, Jun 13, 2015 at 7:52 PM, Yann Ylavic
>> > wrote:
>> >>
>> >> On Sat, Jun 13, 2015 at 8:49 PM, Jeff Trawick
>> >> wr
On Sat, Jun 13, 2015 at 7:42 PM, Yann Ylavic wrote:
> On Sun, Jun 14, 2015 at 1:18 AM, Jeff Trawick wrote:
> > On Sat, Jun 13, 2015 at 6:06 PM, Yann Ylavic
> wrote:
> >>
> >> I did not look at pr12355.t and pr43738.t yet, however those passed in
> >> my tests, so it's probably something differe
On Sat, Jun 13, 2015 at 8:25 PM, Yann Ylavic wrote:
> On Sun, Jun 14, 2015 at 2:18 AM, Jeff Trawick wrote:
> > On Sat, Jun 13, 2015 at 7:52 PM, Yann Ylavic
> wrote:
> >>
> >> On Sat, Jun 13, 2015 at 8:49 PM, Jeff Trawick
> wrote:
> >> >
> >> > Those that know the original patch would presumabl
On Sun, Jun 14, 2015 at 2:18 AM, Jeff Trawick wrote:
> On Sat, Jun 13, 2015 at 7:52 PM, Yann Ylavic wrote:
>>
>> On Sat, Jun 13, 2015 at 8:49 PM, Jeff Trawick wrote:
>> >
>> > Those that know the original patch would presumably have a better way to
>> > code this.
>> >
>> > I recall that httpd 1
On Sat, Jun 13, 2015 at 7:52 PM, Yann Ylavic wrote:
> On Sat, Jun 13, 2015 at 8:49 PM, Jeff Trawick wrote:
> >
> > Those that know the original patch would presumably have a better way to
> > code this.
> >
> > I recall that httpd 1.3 generally added whitespace after the chunk size
> as
> > an o
On Sat, Jun 13, 2015 at 8:49 PM, Jeff Trawick wrote:
>
> Those that know the original patch would presumably have a better way to
> code this.
>
> I recall that httpd 1.3 generally added whitespace after the chunk size as
> an optimization (pre-allocating space in BUFF for the largest possible chu
On Sun, Jun 14, 2015 at 1:18 AM, Jeff Trawick wrote:
> On Sat, Jun 13, 2015 at 6:06 PM, Yann Ylavic wrote:
>>
>> I did not look at pr12355.t and pr43738.t yet, however those passed in
>> my tests, so it's probably something different.
>
>
> Just in case it wasn't clear, these aren't regressions.
On Sat, Jun 13, 2015 at 6:06 PM, Yann Ylavic wrote:
> On Sat, Jun 13, 2015 at 6:51 PM, Rainer Jung
> wrote:
> >
> > any chance you can reproduce the problem with a slightly patched 2.4.14
> to
> > get additional log output around the suspect code?
> >
> > The patch would be
> >
> > Index: module
On Sat, Jun 13, 2015 at 6:51 PM, Rainer Jung wrote:
>
> any chance you can reproduce the problem with a slightly patched 2.4.14 to
> get additional log output around the suspect code?
>
> The patch would be
>
> Index: modules/http/http_filters.c
> ==
On Sat, Jun 13, 2015 at 9:24 AM, Jeff Trawick wrote:
> On Thu, Jun 11, 2015 at 10:08 AM, Jim Jagielski wrote:
>
>> The pre-release test tarballs for Apache httpd 2.4.14 can be found
>> at the usual place:
>>
>> http://httpd.apache.org/dev/dist/
>>
>> I'm calling a VOTE on releasing these
On Sat, Jun 13, 2015 at 1:35 PM, Steffen wrote:
>
> Done:
>
>
> [http:error] [pid 6440:tid 1160] (22)Invalid argument: [remote
> 127.0.0.1:81] AH9: Error parsing chunk size, buffer 4c7 \r\n,
> limit 8190
> [proxy_http:error] [pid 6440:tid 1160] (20014)Internal error (specific
> informatio
Not all works with compression disabled in the backend,
there are pages that still does not work:
[http:error] [pid 6728:tid 1160] (22)Invalid argument: [remote 127.0.0.1:81]
AH9: Error parsing chunk size, buffer 1f0 \r\n, limit 8190
[proxy_http:error] [pid 6728:tid 1160] (20014)Internal
When I disable compression in Sambar then it is fine, like with 2.4.13 and
below.
-Original Message-
From: Steffen
Sent: Saturday, June 13, 2015 7:35 PM Newsgroups: gmane.comp.apache.devel
To: dev@httpd.apache.org
Subject: Re: * Re: [VOTE] Release Apache httpd 2.4.14 as GA
Do
Done:
[http:error] [pid 6440:tid 1160] (22)Invalid argument: [remote
127.0.0.1:81] AH9: Error parsing chunk size, buffer 4c7 \r\n,
limit 8190
[proxy_http:error] [pid 6440:tid 1160] (20014)Internal error (specific
information not available): [client ::1:62059] AH01110: error reading
Hi Steffen,
any chance you can reproduce the problem with a slightly patched 2.4.14
to get additional log output around the suspect code?
The patch would be
Index: modules/http/http_filters.c
===
--- modules/http/http_filters.c (
On Sat, Jun 13, 2015 at 9:36 AM, Steffen wrote:
> Debug 2.4.14 was already in my first post.
>
sorry!
>
> The 2.4.13 (no error) and 2.4.14 debug level error.log:
>
> Apache/2.4.13 (Win32)
>
>
> [Sat Jun 13 15:23:23.031198 2015] [authz_core:debug] [pid 9208:tid 1168]
> mod_a
Debug 2.4.14 was already in my first post.
The 2.4.13 (no error) and 2.4.14 debug level error.log:
Apache/2.4.13 (Win32)
[Sat Jun 13 15:23:23.031198 2015] [authz_core:debug] [pid 9208:tid 1168]
mod_authz_core.c(834): [client 127.0.0.1:54501] AH01628: authorization result:
gra
On Thu, Jun 11, 2015 at 10:08 AM, Jim Jagielski wrote:
> The pre-release test tarballs for Apache httpd 2.4.14 can be found
> at the usual place:
>
> http://httpd.apache.org/dev/dist/
>
> I'm calling a VOTE on releasing these as Apache httpd 2.4.14 GA.
>
> [ ] +1: Good to go
> [ ] +0: meh
On Sat, Jun 13, 2015 at 8:31 AM, Steffen wrote:
> Tested with 2.4.13 tarball, then no error.
>
Wow...
Is anything written to the error log when you try proxy to the Sambar
server? If my guess about the related code is correct, you'll need
LogLevel Info (or debug or trace) to see all the releva
Tested with 2.4.13 tarball, then no error.
-Original Message-
From: Steffen
Sent: Saturday, June 13, 2015 1:33 PM Newsgroups: gmane.comp.apache.devel
To: dev@httpd.apache.org
Subject: Re: [VOTE] Release Apache httpd 2.4.14 as GA
Regression: All works fine except a Proxy Pass to Sambar
Regression: All works fine except a Proxy Pass to Sambar server, was
working ok with 2.4.12.
ProxyPasses to other servers the Sambar works fine.
ProxyPass /sysadmin http://127.0.0.1:81/sysadmin
ProxyPassReverse /sysadmin http://127.0.0.1:81/sysadmin
Calling with http://127.0.0.1:8080/
Am 13.06.2015 um 12:23 schrieb Rainer Jung:
Hi Michael,
Am 13.06.2015 um 12:10 schrieb Michael Felt:
Just a link to the "Howto setup Apache::Test" would be sufficient. The
README in the project sends me to mod_perl info, not a list of perl mods
needed to be added -- and unfortunately the Apache
Hi Michael,
Am 13.06.2015 um 12:10 schrieb Michael Felt:
Just a link to the "Howto setup Apache::Test" would be sufficient. The
README in the project sends me to mod_perl info, not a list of perl mods
needed to be added -- and unfortunately the Apache::Test does not
"include" a dependency list e
Just a link to the "Howto setup Apache::Test" would be sufficient. The
README in the project sends me to mod_perl info, not a list of perl mods
needed to be added -- and unfortunately the Apache::Test does not "include"
a dependency list either - or CPAN could do this all automatically.
On Tue, Ju
24 matches
Mail list logo
