apache 2.0.55 doesn't honour KeepAlive
All, There seems to be a problem in our apache set up with KeepAlive. We'd like to set KeepAlive 'Off' due to a non-HTTP 1.1 standards compliant client which expects a new connection per-request - however even when we do this the response headers do not contain "Connection: close". The net result is that apache hangs around for the KeepAlive timeout. Any help much appreciated. Find below configuration details & trace. Thanks, Rolf *Server:* Apache/2.0.55 (Unix) DAV/2 mod_ssl/2.0.55 OpenSSL/0.9.8b mod_perl/2.0.2 Perl/v5.8.7 *OS:* Solaris 10 *httpd.conf fragment:* User"nobody" Group"nobody" ... #needed for http/1.1 testing KeepAlive Off *Request Header:* POST /BDL-Online-Access-Service/Provision HTTP/1.1 Content-Type: text/xml; charset=UTF-8 SOAPAction: "Provision" User-Agent: Axis2 Host: 10.142.10.147:8080 Content-Length: 613 *Response Header:* HTTP/1.1 200 OK Date: Fri, 26 Sep 2008 19:34:35 GMT Server: Apache/2.0.55 (Unix) DAV/2 mod_ssl/2.0.55 OpenSSL/0.9.8b mod_perl/2.0.2 Perl/v5.8.7 Content-Length: 491 Content-Type: text/xml; charset=utf-8 SOAPServer: SOAP::Lite/Perl/0.69
Re: json library
On Sun, Feb 22, 2009 at 4:10 AM, Paul Querna wrote: > i'm somewhat involved with libjsox: > http://code.google.com/p/libjsox/ > > > > Matthew Rushton wrote: > >> Does anyone have any experience with using any of the C JSON libraries to >> encode json in responses? It looks like there are several options, I just >> wanted to know what people are using if anything? Thanks! >> -Matt >> >> >> > I've been using this for 2-3 years now: http://oss.metaparadigm.com/json-c/ Has handled everything chucked at it so far - the core struct makes a good general purpose dynamic data structure as well. Rolf
httpd trunk: Auth changes?
Hi, I've successfully built mod_perl2 against the server trunk recently but the mp test suite fails in a number of places. At the moment I am mainly concerned with the failure of the access tests. The same tests pass when mp2 is built against 2.2.6 httpd. There are rumours of changes to the aaa code early this year; I'd guess this is related to the mp2 access test errors. Can anyone shed any light on what has changed in the server auth mechanism and what the changes might mean for mod_perl? Gratefully, Rolf PS I have tried the mod_perl list.
Re: UDP support in mod_perl2/apache
On 11/14/07, Issac Goldstand <[EMAIL PROTECTED]> wrote: > I just realized that there was a typo in the patchset - it applies > cleanly against httpd-2.2.6, but there's a line that shouldn't be there: > > srclib/apr/network_io/unix/sendrecv.c line 118: > from->salen = sizeof(from->sa); > > Remove this and it should build cleanly. > > Issac > I've now managed to get 2.2.6 patched. I had to tweak a couple of the patches manually. I'll put together a patchfile shortly. Best of all mod_perl2 builds and tests OK - 4 failures in subprocess & 1 in server_constant. This all but removes Issac's UDP patch as a suspect in the case of the mp2- tests-fail -against-httpd-trunk. So now then - how do I set up a UDP service? Is there any special configuration? Rolf
httpd trunk - How to get info that ap_requires used to return
Folks, I want to build mod_perl 2 against httpd trunk but I've encountered a few road-blocks. The one that has held me up recently is to do with the removal of ap_requires from the httpd source sometime since httpd 2.2.6. The mod_perl test suite includes several tests that rely on ap_requires to dig out Require data e.g Require user shaun Require group sheep These obviously now fail when mp is built against the httpd trunk. Presumably there are other straightforward ways to get at the Require configuration for a given directory? I have had a scout round - the mod_authz code uses the require_line data structure but I can't immediately see how this can be related to mod_perl. Thanks, Rolf
Re: httpd trunk - How to get info that ap_requires used to return
>
> My immediate aim is to test Isaac's UDP support patch with mod_perl - I
> want to make a case for apache as a viable alternative for our service
> platform and udp support is essential. If I can get the mod_perl test suite
> to pass I increase the credibility of my proposal.
The mod_perl tests that use ap_requires are quite simple - the Require
lines are retrieved via ap_requires and then the values compared against
data in the current request. Example:
In the conf:
Require user goo bar
Require group bar tar
In the test code:
# extract just the requirement entries
my %require =
map { my ($k, $v) = split /\s+/, $_->{requirement}, 2; ($k, $v||'') }
@{ $r->requires };
debug \%require;
return Apache2::Const::SERVER_ERROR unless $require{user} eq $users;
return Apache2::Const::SERVER_ERROR unless $require{group} eq $groups;
$require{user} should be 'goo bar'
$require{group} should be 'bar tar'
I don't yet have much detailed knowledge of the httpd code - my naive
interpretation is that ap_requires returned a list of require_line structs
where the 'requirement' field is
everything after the 'Require' in the config line. If there was some
way to get a list of the Require statements in the conf file it would
be an easy matter to re-jig the test code.
I suppose I could parse the config file directly (e.g. with Config::General )
to get the Require lines - but I would prefer to use any in-built httpd
support if possible.
>From my naive perspective I'd offer that per-directory queries for
configuration
information such as all Require statements are useful things to have.
I intend no criticism of the re-design.
Regards,
Rolf
Re: httpd trunk - How to get info that ap_requires used to return
Thanks Brad, that certainly clears things up for me. I haven't got time at the moment to work out what the new scheme means for mod_perl in general. For now I will work around it. Rolf
