Woot Woot Woot! We have our wiki!
http://wiki.apache.org/mod_python/
Now comes the hard part... what the heck are we going to do with it? :)
Jim
Graham Dumpleton wrote:
On 13/09/2006, at 8:45 AM, Jim Gallacher wrote:
Woot Woot Woot! We have our wiki!
http://wiki.apache.org/mod_python/
Now comes the hard part... what the heck are we going to do with it? :)
Ahhh, more work. :-(
Obviously the FAQ stuff can go over there, but I
That does work, but it won't get me where I need to be. The problem
is that the spoolfile isn't set after a parsing error - there is no
brigade in param-upload upon a bad parse. I did find a simple way to
get a filter in there:
apreq_hook_t * my_hook_handle = apreq_hook_make(req-pool,
I'm trying to raise my post maximum and keep getting this error:[error] [client 127.0.0.1] (20014)Internal error: Content-Length header (959543540) exceeds configured max_body limit (67108864)How do I set max body higher? So far I have:sub handler { my $r = shift; my $req = Apache2::Request-new(
Hi all,
I've been trying to solve my confusion on the exact order of hooks and
filters being invoked inside an HTTP request, and was wondering why
ap_invoke_filter_init(r-input_filters) is called inside of
ap_invoke_handler (server/config.c:338) ?
I can understand initializing output filters at
If I went to all that trouble to give a line number below, I should
probably mention that I'm looking at the 2.2.3 release. Sorry for not
mentioning that the first time around.
Issac Goldstand wrote:
Hi all,
I've been trying to solve my confusion on the exact order of hooks and
filters
-Ursprüngliche Nachricht-
Von: Issac Goldstand
Gesendet: Dienstag, 12. September 2006 12:04
An: dev@httpd.apache.org
Betreff: why does ap_invoke_handler init input filters?
Hi all,
I've been trying to solve my confusion on the exact order
of hooks and
filters being
I'm currently involved in building a new webserver environment to
replace a 6 year old server running a large website with a fairly broken
publishing model.
One of the things we'd like to do is lock down PHP so that we're no
longer using mod_php running all as one user, and this means using
cgi
On Tue, September 12, 2006 5:26 pm, Ben Charlton wrote:
One of the things we'd like to do is lock down PHP so that we're no
longer using mod_php running all as one user, and this means using
cgi mode under suexec. The kicker is that we can't use a separate vhost
for each department/publishing
On 12 Sep 2006, at 22:27, [EMAIL PROTECTED] wrote:
--- Additional Comments From [EMAIL PROTECTED] 2006-09-12
21:27 ---
The PUT handler is a small 10 line script. It absolutely doesn't
return a code
70007 or anything other than 0 no matter how it finishes.
This is not resolved
On Thu, 7 Sep 2006, Philip M. Gollucci wrote:
A release candidate for Apache-Test 1.29-RC1 is now available.
http://people.apache.org/~pgollucci/at/Apache-Test-1.29-rc1.tar.gz
+1. Tested on
- Win32: Apache/2.2.3 (winnt)
- linux: Apache/2.0.55 (prefork)
--
best regards,
Randy
11 matches
Mail list logo