Hello,
I'm very new to developing Input Filters with Apache. I have written an
input filter to read the request body content and print it to my error log.
I have two print statements in my filtering function (one to let me know
that my filter code has been called and the other to print the
Is util_filter.h lacking a closing in the #include ?
On 1/16/12, Pranesh Vadhirajan vadhira...@teralogics.com wrote:
Hello,
I'm very new to developing Input Filters with Apache. I have written an
input filter to read the request body content and print it to my error log.
I have two print
I believe it's a header that is included in the Apache build, so I would
think it doesn't have that issue.
Thanks,
Pranesh
-Original Message-
From: Arturo 'Buanzo' Busleiman [mailto:bua...@buanzo.com.ar]
Sent: Monday, January 16, 2012 11:18 AM
To: modules-dev@httpd.apache.org
Subject:
I think he meant on your include line :
#include apr_buckets.h
#include util_filter.h
stat
On 01/16/2012 09:37 AM, Pranesh Vadhirajan wrote:
I believe it's a header that is included in the Apache build, so I would
think it doesn't have that issue.
Thanks,
Pranesh
-Original
Sorry, that was just a typo. The include does have the closing in my source
file.
Thanks,
Pranesh
-Original Message-
From: Joe Lewis [mailto:jle...@silverhawk.net] On Behalf Of Joe Lewis
Sent: Monday, January 16, 2012 11:38 AM
To: modules-dev@httpd.apache.org
Subject: Re: Input
Thanks for the response, Joe. Are the ap_*log lines to be used in lieu of
the fprintfs that I have? Or do those actually display errors during
compilation of my code through apxs?
Thanks,
Pranesh
-Original Message-
From: Joe Lewis [mailto:jle...@silverhawk.net] On Behalf Of Joe Lewis
Thanks for the understanding.
Experience is that win issues hardly land in the status. Mostly the answer is
make a bug report, and it is of the table and sitting as reported bug for a
very long time. Take for example the serious bug from Mario about the balancer
in 2.3. An other are the
On 16 Jan 2012, at 2:31 PM, Steffen wrote:
Thanks for the understanding.
Experience is that win issues hardly land in the status. Mostly the answer is
make a bug report, and it is of the table and sitting as reported bug for a
very long time. Take for example the serious bug from Mario
Bojan Smojver wrote:
On Sun, 2012-01-15 at 18:06 +0100, Bert Huijben wrote:
If the timer has enough detail we could just use the time, ptr
combination as the seed here.
See whether you like r1231858.
r1231605 and r1231858 cause massive regressions and test case failures in httpd.
Not
Also I cannot believe that eg the rewrite p issue was/is(?) only win.
It wasn't windows-only.
Unbelievable this answer, I am stimulating users to use it and with success. I
feel, you are accusing me here and the windows community. No problem, we are
continuing to let you know what issues we discover. In principal up to you how
you handle issues Keep in mind we are just users, no dev's.
I will be doing the TR of Apache httpd 2.4.0 later on today...
w00t!
On Mon, Jan 16, 2012 at 2:47 PM, Jim Jagielski j...@jagunet.com wrote:
I will be doing the TR of Apache httpd 2.4.0 later on today...
w00t!
Sorry to be a user poking in to the dev list, but will 2.4.0 be GA, or
will GA be a later release in the 2.4 series?
Cheers
Tom
It will be GA.
On Jan 16, 2012, at 10:25 AM, Tom Evans wrote:
On Mon, Jan 16, 2012 at 2:47 PM, Jim Jagielski j...@jagunet.com wrote:
I will be doing the TR of Apache httpd 2.4.0 later on today...
w00t!
Sorry to be a user poking in to the dev list, but will 2.4.0 be GA, or
will GA be a
I forgot to mention in my original email, that I'm receiving segmentation
faults, but I'm not sure what part of my code is causing this.
Pranesh
-Original Message-
From: Pranesh Vadhirajan [mailto:vadhira...@teralogics.com]
Sent: Monday, January 16, 2012 11:41 AM
To:
You can do two things.
Place some ap_*log debug lines in your code and compile to find the
line, or use the Gnu debugger and step through apache until you get the
segmentation fault.
On 01/16/2012 10:45 AM, Pranesh Vadhirajan wrote:
I forgot to mention in my original email, that I'm
The 2.4.0 (prerelease) tarballs are available for download and test:
http://httpd.apache.org/dev/dist/
I'm calling a VOTE on releasing these as Apache httpd 2.4.0 GA.
Vote will last the normal 72 hours... Can I get a w00t w00t!
On 16 Jan 2012, at 17:50, Jim Jagielski wrote:
The 2.4.0 (prerelease) tarballs are available for download and test:
http://httpd.apache.org/dev/dist/
I'm calling a VOTE on releasing these as Apache httpd 2.4.0 GA.
Vote will last the normal 72 hours... Can I get a w00t w00t!
$
On 16 Jan 2012, at 17:50, Jim Jagielski wrote:
The 2.4.0 (prerelease) tarballs are available for download and test:
http://httpd.apache.org/dev/dist/
I'm calling a VOTE on releasing these as Apache httpd 2.4.0 GA.
Vote will last the normal 72 hours... Can I get a w00t w00t!
I
On Monday 16 January 2012, Tim Bannister wrote:
On 16 Jan 2012, at 17:50, Jim Jagielski wrote:
The 2.4.0 (prerelease) tarballs are available for download and
test:
http://httpd.apache.org/dev/dist/
I'm calling a VOTE on releasing these as Apache httpd 2.4.0 GA.
Vote will last
On 16 Jan 2012, at 22:31, Stefan Fritsch wrote:
There has been a change in 2.3/2.4: You need to download and extract the
*-deps tarball as well if you want to use --with-included-apr.
That's not documented in http://httpd.apache.org/docs/2.4/install.html
Is it also worth adding a note to
On 16 Jan 2012, at 7:50 PM, Jim Jagielski wrote:
The 2.4.0 (prerelease) tarballs are available for download and test:
http://httpd.apache.org/dev/dist/
I'm calling a VOTE on releasing these as Apache httpd 2.4.0 GA.
Vote will last the normal 72 hours... Can I get a w00t w00t!
+1.
On Mon, Jan 16, 2012 at 12:50 PM, Jim Jagielski j...@jagunet.com wrote:
The 2.4.0 (prerelease) tarballs are available for download and test:
http://httpd.apache.org/dev/dist/
I'm calling a VOTE on releasing these as Apache httpd 2.4.0 GA.
Vote will last the normal 72 hours... Can I
On 1/16/2012 11:50 AM, Jim Jagielski wrote:
The 2.4.0 (prerelease) tarballs are available for download and test:
http://httpd.apache.org/dev/dist/
Congratulations.
If your response;
From: Jim Jagielski j...@jagunet.com
In-Reply-To: 6f572370-958f-4b06-9751-504701e54...@apachelounge.com
On 1/16/2012 10:55 PM, William A. Rowe Jr. wrote:
On 1/16/2012 11:50 AM, Jim Jagielski wrote:
The 2.4.0 (prerelease) tarballs are available for download and test:
http://httpd.apache.org/dev/dist/
[...]
then I have no reason to test. -1 to release. Learn tact, man.
To further
25 matches
Mail list logo
