> On Mar 19, 2016, at 5:05 PM, Yann Ylavic wrote:
>
>
> Anyway, this is really cool stuff!
>
Thanks! It is one thing that nginx has that we don't.
Of course, we also have lots of stuff that nginx doesn't
but that doesn't seem to sway lots of people ;)
> On Mar 19, 2016, at 5:05 PM, Yann Ylavic wrote:
>
>
> However, it seems that there are some paths where the worker threads
> can allocate on (or use) the server config pool (ctx->p, a subpool of
> pconf).
> This (AFAICT) concerns hc_get_hcworker(),
> On Mar 19, 2016, at 5:05 PM, Yann Ylavic wrote:
>
> The proposed backport patch (v2) does not contain mod_proxy_hcheck.c
> itself
Actually, it does:
http://home.apache.org/~jim/patches/hcheck-2.4-v2.patch
...
diff --git a/modules/proxy/mod_proxy_hcheck.c
I promise to look deeply into this post 2.4.19 release.
> On Mar 19, 2016, at 1:09 PM, montt...@heavyspace.ca wrote:
>
> Since its been a while since this issue was mentioned, this patch allows
> Apache to suexec files by a different (but still restricted by UID) owner, to
> avoid the security
Hmmm a rough look doesn't seem to show anyplace where we
used to use strcasecmp and now use strcmp;
The bigger question is whether or not 'none' should be case insensitive
or not. IMHO, it should be.
> On Mar 19, 2016, at 11:31 AM, Michael Kaufmann
> wrote:
>
>
I hope to T 2.4.19 on Mon/Tues with a release on Friday.
There are some backports proposed that would be nice to get
into this release, otherwise I am shooting for a quick release
also around the ACNA time-frame.
test 27 in t/modules/rewrite.t at line 85
> On Mar 14, 2016, at 10:03 AM, Ruediger Pluem <rpl...@apache.org> wrote:
>
>
>
> On 03/14/2016 02:55 PM, Jim Jagielski wrote:
>>
>>> On Mar 14, 2016, at 4:48 AM, Ruediger Pluem <rpl...@apache.org> wrote:
> On Mar 14, 2016, at 7:07 AM, Graham Leggett wrote:
>
> On 14 Mar 2016, at 10:32 AM, Yann Ylavic wrote:
>
>> Since apr_pollfd_t is not opaque (unlike apr_socket_t), maybe we could
>> remove the indirection here (and in the code below) with somthing
> On Mar 14, 2016, at 4:48 AM, Ruediger Pluem wrote:
>
>
> This seems to cause frequent (no always) failures with test 8 of
> t/ssl/proxy.t.
> The request times out with a 504 status. So it looks like the "backend" in
> this request does not respond.
> Used MPM is Event,
I've given it a quick look-thru and I. Am. Impressed.
This is more Super Cool Mojo!
> On Mar 12, 2016, at 10:46 AM, Graham Leggett wrote:
>
> Hi all,
>
> The following patch provides support for TCP proxying to httpd.
>
> It consists of the following three parts:
>
> -
Go ahead and propose for backport... it will require 3 +1s
for inclusion.
> On Mar 9, 2016, at 7:53 AM, Stefan Eissing
> wrote:
>
> I propose to backport mod_proxy_http2 to 2.4.x as an experimental
> module with the same restrictions as mod_http2.
>
> Purpose:
>
Thank you for your email. I am forwarding this to the
correct Email list, which is dev@httpd.apache.org.
> On Mar 8, 2016, at 11:28 AM, t...@able.be wrote:
>
> Hi,
>
> I'm currently testing a Web socket application behind an apache reverse
> proxy. I started off with apache version 2.4.12, but
Intstead of adding YAD (yet another directive ;) ), would it
be possible to somehow leverage Listen itself, maybe with some
sort of flag?
> On Mar 7, 2016, at 6:41 AM, Jan Kaluža wrote:
>
> Hi,
>
> attached patch adds new "FreeListen" directive. The difference between
>
For historical purposes :)
[13:25:42] jimjag: I'll let monttyle respond on-list, but his
attack vector (at least, as I understood it) was as follows:
[13:26:39] attacker uses a one-time vulnerability in a CGI script
to modify the script itself (or anything in the parent directory) and thus
> On Feb 29, 2016, at 11:22 AM, montt...@heavyspace.ca wrote:
>
> I understand the point of not allowing apache to suexec any
> arbitrary file, and matching user:group makes sense to an extent.
> But using user:group as blind labels ignores what these permissions
> really mean to the kernel.
; Am 03.03.2016 um 16:21 schrieb Yann Ylavic <ylavic@gmail.com>:
>>
>> On Thu, Mar 3, 2016 at 3:57 PM, Jim Jagielski <j...@jagunet.com> wrote:
>>> /** Config vector containing pointers to connections per-server
>>>* config structures. */
>>>
Forgot to mention that it's created w/ ptrans which is c->pool
> On Mar 3, 2016, at 9:57 AM, Jim Jagielski <j...@jagunet.com> wrote:
>
>/** Config vector containing pointers to connections per-server
> * config structures. */
>struct ap_conf_vector_t *conn_config;
>
/** Config vector containing pointers to connections per-server
* config structures. */
struct ap_conf_vector_t *conn_config;
Attached... just in case
svn.merge
Description: Binary data
svn.record
Description: Binary data
> On Mar 2, 2016, at 2:10 PM, Jim Jagielski <j...@jagunet.com> wrote:
>
> yeah, I use svn.merge and svn.record (for those cases where
> I use a actual patch file, but want
yeah, I use svn.merge and svn.record (for those cases where
I use a actual patch file, but want to record the SVN metadata)
> On Mar 2, 2016, at 11:13 AM, Yann Ylavic wrote:
>
> re: mod_proxy_hcheck backport
>
>> ylavic: Looks like the changes on struct proxy_worker_shared would break
>> startup with "BalancerPersist on" due to the strict checks on
>> the sizes
water temperature...
>
>> Am 02.03.2016 um 12:22 schrieb Jim Jagielski <j...@jagunet.com>:
>>
>> I would think that it is not covered under the http2 exception
>> and would require a backport proposal and vote...
>>
>>> On Mar 2, 2016, at
I would think that it is not covered under the http2 exception
and would require a backport proposal and vote...
> On Mar 2, 2016, at 5:06 AM, Stefan Eissing
> wrote:
>
> to backport or not to backport that is the question. opinions?
> On Mar 1, 2016, at 7:09 PM, Graham Leggett wrote:
>
> Hi all,
>
> In order to get connections to have async behaviour, it must be possible for
> the process_connection hook to exit in the expectation of being called again
> when an async mpm is present - this is easy, the
> On Mar 1, 2016, at 9:46 AM, Graham Leggett <minf...@sharp.fm> wrote:
>
> On 29 Feb 2016, at 10:33 PM, Jim Jagielski <j...@jagunet.com> wrote:
>
>> I've been digging into how we could better leverage serf on the mod_proxy
>> side w/o going the route of m
I'd prefer we use a define, eg:
#define PROXY_WORKER_RFC1035_SIZE 512
rather than embedding magic numbers...
> On Feb 29, 2016, at 8:20 PM, yla...@apache.org wrote:
>
> Author: ylavic
> Date: Tue Mar 1 01:20:06 2016
> New Revision: 1732986
>
> URL:
> On Feb 26, 2016, at 12:06 PM, Stefan Eissing
> wrote:
>
>- And: it could be done for mod_proxy_http, too! I see no reason why a
> single
> thread cannot use pollsets to juggle a couple of http/1.1 backend
> connections
> on top of a http/2 master
> On Feb 29, 2016, at 7:43 AM, Yann Ylavic wrote:
>
> Hi,
>
> On Mon, Feb 29, 2016 at 1:31 PM, Bruno Raoult wrote:
>>
>> I did find a bug in mod_autoindex more than one year ago, about missing CSS
>> class, and proposed a patch at same time
>>
show_bug.cgi?id=59045.
> If this will be fixed with 2.4.19, please go ahead. :)
>
> Regards,
> Micha
>
>> -----Ursprüngliche Nachricht-
>> Von: Jim Jagielski [mailto:j...@jagunet.com]
>> Gesendet: Montag, 29. Februar 2016 13:10
>> An: httpd <dev@htt
It's about time for us to consider another release of the 2.4
branch... We've accumulated some good stuff, with some other
potential backports which could be *very* cool folded into
2.4.19...
Looking at early/mid March and I'll be serving as RM.
Get those votes and backports in!
> On Feb 26, 2016, at 7:50 PM, montt...@heavyspace.ca wrote:
>
> This is not a question on how to use suexec, that's fairly clear. The
> strict, hardwired conditions its willing to suexec under are also spelled out
> pretty clear. My question is the nature of these requirements -- why
Any hints would be appreciated...
I'd also like to dig deeper into using it.
> On Feb 26, 2016, at 10:54 AM, Eric Covener wrote:
>
> Whoops, I realized this is not true -- it's got some modules, but it
> didn't have MY modules -- notably my MPM.
>
> On Fri, Feb 26, 2016 at
That's cool to know! Thx.
> On Feb 22, 2016, at 12:09 PM, Kurt Newman wrote:
>
> If it’s any consolation, cPanel changed our default web server from 2.2 to
> 2.4 on May 2015. We still see a large percentage of customers using 2.2
> though.
>
>> On Feb 15, 2016, at
Aww... I like using 'automagically'... but maybe that's
too old school :)
> On Feb 22, 2016, at 2:18 AM, elu...@apache.org wrote:
>
> Author: elukey
> Date: Mon Feb 22 07:18:19 2016
> New Revision: 1731594
>
> ==
> ---
Required additional change to httpd.h but
applied in r1730723
> On Feb 14, 2016, at 10:31 AM, Jim Jagielski <j...@jagunet.com> wrote:
>
> Thx. Will review asap.
>
>> On Feb 13, 2016, at 8:01 PM, Yehuda Katz <yeh...@ymkatz.net> wrote:
>>
>> Hello al
> On Feb 12, 2016, at 4:48 PM, Eric Covener wrote:
>
>
> Moreso trying to flush out if it's a good or bad idea, seems simple
> enough to add to rotatelogs rather than requiring the wrapper.
Yeah, I would agree...
> On Feb 16, 2016, at 4:08 AM, Plüm, Rüdiger, Vodafone Group
> <ruediger.pl...@vodafone.com> wrote:
>
>
>
>> -Ursprüngliche Nachricht-
>> Von: Jim Jagielski [mailto:j...@jagunet.com]
>> Gesendet: Montag, 15. Februar 2016 23:51
>> An
The more I think of it, the more I think we should just
remove motorz and simple from trunk... Or keep them around
but not really worry about them.
The fun and interesting stuff is already in event, and although
it might be nice to, for example, move the worker_pool stuff
to a simply
Anyone had a chance yet to play around and/or hack on the
motorz mpm yet... I plan on jumping back in on it and was curious
if people had fixes, etc that they were working on.
Thx. Will review asap.
> On Feb 13, 2016, at 8:01 PM, Yehuda Katz wrote:
>
> Hello all,
> I looked into the missing 451 status code because someone asked about it on
> the users list. It seems like a simple enough patch - since it is just
> copying an existing feature.
> I
/me like
> On Feb 12, 2016, at 7:20 AM, Daniel Gruno wrote:
>
> Hi folks,
> as some may know, ComDev is trialling a new thing called 'Help Wanted!'
> at https://helpwanted.apache.org/
>
> I've added a few example entries for httpd, and I'm wondering if this is
> something
Blocking OPTIONS has a long and illustrious history...
I am -0 on doing anything more related to it ;)
The patchfile, minus docs, can be found at:
http://home.apache.org/~jim/patches/hcheck-2.4.patch
Thx!
I am following the way we've handled that struct before when
we've needed to adjust (eg: uds_path)...
> On Feb 12, 2016, at 9:14 AM, Yann Ylavic <ylavic@gmail.com> wrote:
>
> On Fri, Feb 12, 2016 at 2:50 PM, Jim Jagielski <j...@jagunet.com> wrote:
>> The patchfil
I am sending a trial balloon up regarding the viability
of proposing mod_proxy_hcheck be backported to 2.4.x...
If this sounds like a Good Idea, I will work on said
proposal.
> On Feb 11, 2016, at 10:27 AM, Eric Covener <cove...@gmail.com> wrote:
>
> On Thu, Feb 11, 2016 at 10:25 AM, Jim Jagielski <j...@jagunet.com> wrote:
>> I am sending a trial balloon up regarding the viability
>> of proposing mod_proxy_hcheck be backported to 2.
I was wondering about whether we should update the feather[1] with the new
one...
I can do it...
1. https://httpd.apache.org/images/httpd_logo_wide_new.png
--
Sent via Pony Mail for dev@httpd.apache.org.
View this email online at:
https://pony-poc.apache.org/list.html?dev@httpd.apache.org
A rough and very brief framework of such a guide is now available...
http://httpd.apache.org/docs/trunk/howto/reverse_proxy.html
On 2016-02-10 06:21, Luca Toscano wrote:
> 2016-02-10 10:33 GMT+01:00 Stefan Eissing :
>
> > If you write
It looks like the whole retry was removed :(
> On Feb 10, 2016, at 2:21 PM, Ruediger Pluem wrote:
>
>
>
> On 02/10/2016 12:38 AM, yla...@apache.org wrote:
>> Author: ylavic
>> Date: Tue Feb 9 23:38:59 2016
>> New Revision: 1729507
>>
>> URL:
Work in progress in:
docs/manual/howto/reverse_proxy.xml
cheers!
a.de> wrote:
>> Am 09.02.2016 um 13:25 schrieb Jim Jagielski:
>>> We currently have really really little info about the balancer-manager in
>>> our docs, just a short little blurb on how to enable it and a brief
>>> description of what it does [1]. I'd l
We currently have really really little info about the balancer-
manager in our docs, just a short little blurb on how to enable
it and a brief description of what it does [1]. I'd like to extend
that, but does it make sense to add it to the mod_proxy_balancer
module page, or have a separate page
Why the change to modules/proxy/mod_proxy_hcheck.c?
> On Feb 9, 2016, at 10:58 AM, Yann Ylavic wrote:
>
>
> On Feb 9, 2016, at 11:49 AM, Yann Ylavic <ylavic@gmail.com> wrote:
>
> On Tue, Feb 9, 2016 at 5:42 PM, Jim Jagielski <j...@jagunet.com> wrote:
>> Why the change to modules/proxy/mod_proxy_hcheck.c?
>
> The call to ap_proxy_connect_b
very very cool!
> On Feb 8, 2016, at 12:07 PM, Stefan Eissing
> wrote:
>
> FYI: I just checked in a very experimental mod_proxy_http2 that registers on
> h2:// and h2c:// proxy URLs. I did this naming to have the module totally
> separate from mod_proxy_http,
>
>
>
>
> 2016-02-05 17:08 GMT+03:00 Alexey Melezhik <melez...@gmail.com>:
>> 2016-02-05 17:01 GMT+03:00 Jim Jagielski <j...@jagunet.com>:
>>> Personally, I like the idea of having another framework;
>>> the current one is OK but somewhat &q
Personally, I like the idea of having another framework;
the current one is OK but somewhat "painful" to update.
I wonder how possible it would be to transcode the old tests
to Swat? We could then provide for 2 testing frameworks, one
developed by the ASF and the other external and 3rd party.
>
> On Feb 3, 2016, at 3:10 AM, Plüm, Rüdiger, Vodafone Group
> <ruediger.pl...@vodafone.com> wrote:
>
>
>
>> -Original Message-
>> From: Jim Jagielski [mailto:j...@jagunet.com]
>> Sent: Dienstag, 2. Februar 2016 22:44
>> To: httpd
&
> On Feb 3, 2016, at 9:09 AM, Jim Jagielski <j...@jagunet.com> wrote:
>
>
> Right now, the health check module only worries about checking
> workers which are USABLE, which is a worker which is !DISABLED
> and !STOPPED and !IN_ERROR (basically).
>
Actually, that's
> On Feb 3, 2016, at 9:37 AM, Yann Ylavic <ylavic@gmail.com> wrote:
>
> On Wed, Feb 3, 2016 at 3:21 PM, Jim Jagielski <j...@jagunet.com> wrote:
>>
>> Sooo
>>
>> STOPPED: Never sent proxy traffic. Never health-checked. Never
>&g
> On Feb 3, 2016, at 7:30 AM, Yann Ylavic <ylavic@gmail.com> wrote:
>
> On Wed, Feb 3, 2016 at 1:25 PM, Jim Jagielski <j...@jagunet.com> wrote:
>>
>> I WAS thinking about basically "making" HC_FAIL STOPPED because
>> that mode can only be
> On Feb 3, 2016, at 11:56 AM, Tim Bannister <is...@c8h10n4o2.org.uk> wrote:
>
> On 3 February 2016 14:21:58 GMT, Jim Jagielski <j...@jagunet.com> wrote:
>
>> STOPPED: Never sent proxy traffic. Never health-checked. Never
>>re-tried. Never autom
As people can see, if following the commit list, I've been
plugging away on the health check functionality. I just finished
making the HC params dynamically adjustable via the balancer-
manager. Need to do some more error checking, but I think
the rough spots are smoothed down.
Comments
Getting back to this discussion...
Right now we have:
o #define PROXY_WORKER_DISABLED 0x0020
o #define PROXY_WORKER_STOPPED0x0040
o #define PROXY_WORKER_IN_ERROR 0x0080
o #define PROXY_WORKER_HC_FAIL0x0400
Are these bit flags part of our API?? Could I,
Thx... looks good via inspection. Not tested though.
> On Feb 1, 2016, at 1:25 PM, Jacob Champion wrote:
>
> Hi all,
>
> I posted a four-patch set for apxs -- two functionality changes, and two
> cosmetic/refactoring changes -- last week after a quick conversation with
Looks like this is "fallout" from:
http://svn.apache.org/viewvc?view=revision=1707230
> On Jan 31, 2016, at 9:41 PM, Joachim Achtzehnter wrote:
>
> After upgrading from 2.4.12 to 2.4.18 we find that some requests for files
> cause a lock-up when HTTPS is used, but not
> On Jan 30, 2016, at 6:59 PM, NormW wrote:
>
> G'Day,
> Wouldn't an awk script simplify symbol extraction from proxy_util and obviate
> the need for tweaking manual lists?
>
awk or perl or something, yeah :)
Applied!
> On Jan 30, 2016, at 6:59 PM, NormW wrote:
>
>
Looks good to me... If it results in problems or issues,
we'll fix 'em as the come along ;)
> On Jan 29, 2016, at 8:01 AM, Stefan Eissing
> wrote:
>
> I would like to propose some additions to event that help me get rid of two
> ugly hacks in mod_http2:
>
> 1.
My proposed session for the Great Wide Open conference[1]
about Apache httpd 2.4 has been accepted!
1. http://greatwideopen.org/schedule/
Anymore thoughts about this? I'd like to start work on
this while I make some of the hcheck params changable via
the balancer-manager.
> On Jan 27, 2016, at 4:02 AM, Plüm, Rüdiger, Vodafone Group
> wrote:
>
>
>
>> -Original Message-
>> From: Yann Ylavic [mailto:ylavic@gmail.com]
>> Sent: Mittwoch, 27. Januar 2016 09:15
>> To: httpd-dev
>> Subject: Re: svn commit: r1726787 -
>>
Currently, the idea and "logic" associated w/ stopped and disabled
workers are kind of similar. There is a higher concept that one is
more 'admin' controlled and the other more 'autonomous' controlled,
but we really don't enforce any sort of conditions related to that.
I think it's time we start
<wr...@rowe-clan.net> wrote:
>
> What semantics do you suggest for each?
>
> True that they have been effectively identical (and redundant) so far...
>
> On Jan 26, 2016 12:41, "Jim Jagielski" <j...@jagunet.com> wrote:
> Currently, the idea and "
> On Jan 26, 2016, at 2:27 PM, Ruediger Pluem <rpl...@apache.org> wrote:
>
>
>
> On 01/26/2016 08:11 PM, Jim Jagielski wrote:
>> My thoughts are that STOPPED means that health checks won't be
>> done, nor will retry be done. It means stopped-and-won't-au
> On Jan 8, 2016, at 9:45 PM, Daniel Ruggeri wrote:
>
> *The probes to different backends should be done in parallel rather than
> serially to avoid pileups due to a slow responder
I just implemented use of a threadpool to accommodate that. ;)
SendingNWGNUproxy
Transmitting file data .done
Committing transaction...
Committed revision 1726453.
All done! Thx!
> On Jan 23, 2016, at 4:14 PM, NormW wrote:
>
> Greetings all for 2016.
> Can someone with commit clout add the attached diff to httpd-trunk please?
>
I had some cycles before the snow hit so added usage
of threadpools, so that the checks are done in parallel
rather than series...
Quick impl.
> On Jan 22, 2016, at 12:36 PM, Yann Ylavic <ylavic@gmail.com> wrote:
>
> On Fri, Jan 22, 2016 at 6:29 PM, Jim Jagielski <j...@
> On Jan 22, 2016, at 3:55 PM, Christophe JAILLET
> wrote:
>
> Hi,
>
> My 2 cents on mod_proxy_hc:
>
>
> 1) around line 278:
>
> I think that a:
>template->hcexpr = NULL;
> is missing.
>
Thx.
>
>
> 2) line 363
>r->protocol = (char*)"HTTP/1.1";
>
+1
> On Jan 22, 2016, at 9:17 AM, Stefan Eissing
> wrote:
>
>
>> Am 22.01.2016 um 15:16 schrieb Eric Covener :
>>
>> On Fri, Jan 22, 2016 at 9:12 AM, Stefan Eissing
>> wrote:
>>> With the timeout behaviour of SSL
At this point GET is now implemented as well as checking
the response via ap_expr...
I think this is at a stage to let it sit for a bit
and have people whack away at it.
I have some ideas on extending it to use a thread-pool
in the watchdog, to allow for parallel health-checks.
Eventually, using
I think that we should always ensure that mod_status provides the info and
insight that our users want and need, so +1 on adding fields and columns
as required.
It *might* make sense to add them at the end, almost as if we were
adding additional fields to a struct and wanted to maintain an API,
Thx!
BTW, do you have pointers on how to use your "new" Coccinelle/spatch
script to assign AH log numbers?
> On Jan 19, 2016, at 2:44 PM, Rainer Jung <rainer.j...@kippdata.de> wrote:
>
> Am 19.01.2016 um 20:02 schrieb Jim Jagielski:
>> Ahhh... yeah, I gues
Sounds good to me!!
thx!
> On Jan 21, 2016, at 10:23 AM, Rainer Jung wrote:
>
> I should have asked earlier: wouldn't it be more suitable to implement to
> response body as a variable instead of a function?
>
> When looking at server/util_expr_eval.c, I find
THX!
> On Jan 21, 2016, at 10:12 AM, Rainer Jung <rainer.j...@kippdata.de> wrote:
>
> Hi Jim,
>
> Am 21.01.2016 um 15:35 schrieb Jim Jagielski:
>> BTW, do you have pointers on how to use your "new" Coccinelle/spatch
>> script to assign AH l
; On Thu, Jan 21, 2016 at 4:25 PM, Jim Jagielski <j...@jagunet.com> wrote:
>> Sounds good to me!!
>>
>> thx!
>>
>>> On Jan 21, 2016, at 10:23 AM, Rainer Jung <rainer.j...@kippdata.de> wrote:
>>>
>>> I should have asked earlier: wou
Not seeing a mmn bump... ?
> On Jan 21, 2016, at 11:36 AM, ic...@apache.org wrote:
>
> Author: icing
> Date: Thu Jan 21 16:36:33 2016
> New Revision: 1726009
>
> URL: http://svn.apache.org/viewvc?rev=1726009=rev
> Log:
> scoreboard addition of protocol, new ap_udpte_child_status methods
>
>
Did you want me to work on it, or are you?
> On Jan 21, 2016, at 10:25 AM, Jim Jagielski <j...@jagunet.com> wrote:
>
> Sounds good to me!!
>
> thx!
>
>> On Jan 21, 2016, at 10:23 AM, Rainer Jung <rainer.j...@kippdata.de> wrote:
>>
>> I should
Where are we with this? Trunk uses this. Should a backport
proposal be done for 2.4??
even better!
sounds cool.
> On Jan 21, 2016, at 11:51 AM, Rainer Jung <rainer.j...@kippdata.de> wrote:
>
> Am 21.01.2016 um 17:03 schrieb Jim Jagielski:
>> Did you want me to work on it, or are you?
>
> I just had some late lunch and started to think closer a
I get:
AH00102: [Thu Jan 21 18:05:44 2016] file util_expr_eval.c, line 218,
assertion "data != ((void*)0)" failed
> On Jan 21, 2016, at 12:50 PM, Rainer Jung <rainer.j...@kippdata.de> wrote:
>
> Am 21.01.2016 um 17:55 schrieb Jim Jagielski:
>> even better!
reak;
Specifically:
*parms->data = NULL;
> On Jan 21, 2016, at 1:08 PM, Jim Jagielski <j...@jagunet.com> wrote:
>
> That is with:
>
> ProxyHCExpr foof2 {hc('body') !~ /domain is established/}
>
> With
>
> ProxyHCExpr foof2 {kept_body('body') !~ /doma
As I read ap_expr, it should be:
diff --git a/modules/proxy/mod_proxy_hcheck.c b/modules/proxy/mod_proxy_hcheck.c
index 1667e77..b211d1c 100644
--- a/modules/proxy/mod_proxy_hcheck.c
+++ b/modules/proxy/mod_proxy_hcheck.c
@@ -987,7 +987,7 @@ static int hc_expr_lookup(ap_expr_lookup_parms *parms)
This implies that the kept_body() func added to ap_expr should
be removed, right?
> On Jan 21, 2016, at 12:49 PM, rj...@apache.org wrote:
>
> Author: rjung
> Date: Thu Jan 21 17:49:21 2016
> New Revision: 1726038
>
> URL: http://svn.apache.org/viewvc?rev=1726038=rev
> Log:
> Implement expr
BTW: that is so cool. No idea we could do that w/ ap_expr!
> On Jan 21, 2016, at 12:55 PM, Jim Jagielski <j...@jagunet.com> wrote:
>
> This implies that the kept_body() func added to ap_expr should
> be removed, right?
>
>> On Jan 21, 2016, at 12:49 PM, rj...@apac
That is with:
ProxyHCExpr foof2 {hc('body') !~ /domain is established/}
With
ProxyHCExpr foof2 {kept_body('body') !~ /domain is established/}
it works as expected.
Thx!
> On Jan 21, 2016, at 1:06 PM, Jim Jagielski <j...@jagunet.com> wrote:
>
> I get:
>
>AH00102:
> On Jan 21, 2016, at 1:19 PM, Rainer Jung wrote:
>
> Can you provide a simple but somehow complete proxy_hcheck config snippet?
> I'll set up a test and check what's wrong.
>
> Regards,
>
A very simple one is:
ProxyHCExpr foof2 {hc('body') !~ /domain is
That is weird... does this help?
hc->context = (void *)wctx;
??
> On Jan 21, 2016, at 2:59 PM, Rainer Jung wrote:
>
> Probably an alignment problem, but I don't immediately see how:
>
> at modules/proxy/mod_proxy_hcheck.c:410
>wctx = 0x70706461
> So this
Hold in a tic... I don't use the context field in ->s.
Based on your stack, then that was the section you hit. But I
have no idea how you hit it. The test is:
if (hc->s->method != worker->s->method)
but neither is ever changed :/
> On Jan 21, 2016, at 3:22 PM, Jim Jagielski <j...@jagunet.com> wrote:
>
> I found one p
801 - 900 of 4498 matches
Mail list logo