Folks,
I'd like to test mp 2.0.3 against the server trunk, primarily so I can
try Issac's UDP support.
With some minor changes to mp2.0.3 I can build successfully but make
test fails in various places. The one that concerns me at the moment
is that t/api/access.t fails.
I have mentioned in an earlier post that I get a 'no authorization
providers configured' message in the error log. For this particular
test I also get 'access to /TestAPI__access failed, reason:
verification of user id '<null>' not configured' in the error log and
'"GET /TestAPI__access HTTP/1.0" 401 535' in the access log.
Now the same test passes when I build the mp 2.0.3 against a 2.2.6
httpd release. So I stuck a bit of debug in both. This is what I get
as a response to a GET in access.t for mp2 vs 2.2.6:
'_rc' => '200',
'_headers' => bless( {
'client-date' => 'Fri, 16 Nov
2007 10:42:22 GMT',
'content-type' => 'text/plain',
'connection' => 'close',
'date' => 'Fri, 16 Nov 2007
10:42:22 GMT',
'client-peer' => '127.0.0.1:8529',
'server' => 'Apache/2.2.6
(Unix) world domination series/2.0 mod_perl/2.0.3 Perl/v5.8.8'
}, 'HTTP::Headers' ),
'_msg' => 'OK',
'_request' => bless( {
'_content' => '',
'_uri' => bless( do{\(my $o =
'http://debian-dev:8529/TestAPI__access')}, 'URI::http' ),
'_headers' => bless( {
'user-agent' => 'libwww-perl/5.808'
},
'HTTP::Headers' ),
'_method' => 'GET'
}, 'HTTP::Request' )
}, 'HTTP::Response' );
In contrast this is what happens for mp2 vs trunk:
<html><head>
<title>401 Authorization Required</title>
</head><body>
<h1>Authorization Required</h1>
<p>This server could not verify that you
are authorized to access the document
requested. Either you supplied the wrong
credentials (e.g., bad password), or your
browser doesn\'t understand how to supply
the credentials required.</p>
<hr>
<address>Apache/2.3.0-dev (Unix) world domination series/2.0
mod_perl/2.0.3 Perl/v5.8.8 Server at debian-dev Port 8529</address>
</body></html>
',
'_rc' => '401',
'_headers' => bless( {
'connection' => 'close',
'date' => 'Fri, 16 Nov 2007
10:44:46 GMT',
'client-peer' => '127.0.0.1:8529',
'content-length' => '535',
'client-date' => 'Fri, 16 Nov
2007 10:44:47 GMT',
'client-warning' => 'Missing
Authenticate header',
'content-type' => 'text/html;
charset=iso-8859-1',
'server' => 'Apache/2.3.0-dev
(Unix) world domination series/2.0 mod_perl/2.0.3 Perl/v5.8.8',
'title' => '401 Authorization Required'
}, 'HTTP::Headers' ),
'_msg' => 'Authorization Required',
'_request' => bless( {
'_content' => '',
'_uri' => bless( do{\(my $o =
'http://debian-dev:8529/TestAPI__access')}, 'URI::http' ),
'_headers' => bless( {
'user-agent' => 'libwww-perl/5.808'
},
'HTTP::Headers' ),
'_method' => 'GET'
}, 'HTTP::Request' )
}, 'HTTP::Response' );
Have there been changes to the way authorisation is handled since
2.2.6? Or is there another way to explain the difference? I've looked
at the dev version of the server documentation but nothing has leapt
out at me.
Thanks,
Rolf
Mail converted by mhonarc 2.6.15
This archive provided courtesy of JSW4.NET, Internet Hosting Services for Small Business.