David Wheeler wrote:
On Tuesday, July 15, 2003, at 01:18 PM, Stas Bekman wrote:
It's trivial. If your webserver supports only the following methods:
GET and HEAD, OPTIONS, but not POST. the request OPTIONS will return a
response with a header Allow: OPTIONS GET HEAD
Oh, I get it. See the
On Friday, July 18, 2003, at 01:37 AM, Stas Bekman wrote:
Done. They will probably require more polishing...
Cool, thanks, I'll take a look in a bit.
I thought I've answered this question already:
http://marc.theaimsgroup.com/?l=apache-test-devm=105772914901179w=2
Right, so you did. I would just
I thought I've answered this question already:
http://marc.theaimsgroup.com/?l=apache-test-devm=105772914901179w=2
Right, so you did. I would just argue that it should default to the
distribution root, but I won't push it. I'm adding this to my Makefile.PL:
use FindBin;
push @ARGV,
On Friday, July 18, 2003, at 09:03 AM, Stas Bekman wrote:
The main reason that the default docroot is t/ is because things like
logs/, conf/, etc are conveniently placed under t/. I'm not quite sure
why do you think that most people will want to have the ../t as the
serverroot. The only
David Wheeler wrote:
On Friday, July 18, 2003, at 07:22 AM, David Wheeler wrote:
Done. They will probably require more polishing...
Cool, thanks, I'll take a look in a bit.
I applied just a bit of polishing. Note that POD has an F tag that's
used for identifying files. This is better than
On Tuesday, July 15, 2003, at 01:18 PM, Stas Bekman wrote:
It's trivial. If your webserver supports only the following methods:
GET and HEAD, OPTIONS, but not POST. the request OPTIONS will return a
response with a header Allow: OPTIONS GET HEAD
Oh, I get it. See the enclosed patch, then.
I
On Wednesday, July 9, 2003, at 01:02 AM, Stas Bekman wrote:
Thank you very much David, I've committed your patches and the docs.
In the future please try to submit each feature change separately.
Thanks.
Okay, no problem.
re: OPTIONS, see section 9.2 in http://www.faqs.org/rfcs/rfc2616.html
David Wheeler wrote:
re: OPTIONS, see section 9.2 in http://www.faqs.org/rfcs/rfc2616.html
[...]
for my $url (@urls) {
my $res = OPTIONS $url;
ok $res-code == 200;
my $allow = $res-header('Allow') || '';
ok $allow =~ /OPTIONS/;
}
I still don't understand what it does or what it's
David Wheeler wrote:
On Monday, June 23, 2003, at 05:08 AM, Geoffrey Young wrote:
I especially need help with the keep_alive parameter to user_agent()
keep_alive enables connection persistence, where the same connection
is used to process multiple requests. the only use of it that I have
seen
On Monday, June 23, 2003, at 05:08 AM, Geoffrey Young wrote:
I especially need help with the keep_alive parameter to user_agent()
keep_alive enables connection persistence, where the same connection
is used to process multiple requests. the only use of it that I have
seen is in
10 matches
Mail list logo
