On 19 May 2011, at 1:06 PM, Yehezkel Horowitz wrote:
Can anyone explain why ap_regexec can take only NULL terminated
string?
I’m working in filter context and want to run regular expression on
bucket content (so I have the buffer length).
Currently I had to copy the bucket content and
I have a patch (based on 2.2.17) to where should I submit it?
From: Graham Leggett [mailto:minf...@sharp.fm]
Sent: Thursday, May 19, 2011 2:23 PM
To: dev@httpd.apache.org
Cc: Anatoli Tubman; Ethan Schorer
Subject: Re: ap_regexec API for buffers (not NULL
On 19 May 2011, at 1:24 PM, Yehezkel Horowitz wrote:
I have a patch (based on 2.2.17) to where should I submit it?
Add it to bugzilla so it doesn't get lost, and then ping here, so
someone can pick it up.
Ideally, the patch should apply to httpd-trunk first, but having a
v2.2 patch also
@httpd.apache.org
Subject: Re: ap_regexec API for buffers (not NULL terminated strings)
On 19 May 2011, at 1:24 PM, Yehezkel Horowitz wrote:
I have a patch (based on 2.2.17) to where should I submit it?
Add it to bugzilla so it doesn't get lost, and then ping here, so someone can
pick it up.
Ideally
On 19 May 2011, at 12:22, Graham Leggett wrote:
On 19 May 2011, at 1:06 PM, Yehezkel Horowitz wrote:
Can anyone explain why ap_regexec can take only NULL terminated string?
Presumably because that's what PCRE supports!
Sounds like a sensible thing to have.
Indeed, I could certainly use
API!
Best regards,
Yehezkel
-Original Message-
From: Nick Kew [mailto:n...@webthing.com]
Sent: Thursday, May 19, 2011 5:27 PM
To: dev@httpd.apache.org
Subject: Re: ap_regexec API for buffers (not NULL terminated strings)
On 19 May 2011, at 12:22, Graham Leggett wrote:
On 19 May
On 19 May 2011, at 15:27, Nick Kew wrote:
Presumably because that's what PCRE supports!
Aaargh! Ignore that. Saw your post and read it as regcomp.
The suggestion is totally sensible as well as trivial. Thank you.
--
Nick Kew
Available for work, contract or permanent
