On Wed, Feb 4, 2015 at 1:42 AM, Scott Lo wrote:
>
>
> --
> Best Regards,
>
> Scott Lo
>
>
--
[image: --]
Nico Coetzee
[image: http://]about.me/nico.coetzee
<http://about.me/nico.coetzee?promo=email_sig>
and... it works now !!
On Tue, Sep 28, 2010 at 8:30 AM, Nico Coetzee wrote:
> $r->status("400");
> $r->status_line("400 Error Baby");
>
> Produces: "HTTP/1.1 400 Error Baby"
>
> And
>
> $r->status("207");
> $r->st
in the main app.
Thanks :-)
On Tue, Sep 28, 2010 at 8:26 AM, William A. Rowe Jr. wrote:
> On 9/28/2010 12:25 AM, Nico Coetzee wrote:
> > The status 400 (with $r->status_line) produces the same result "HTTP/1.1
> 200 OK" and with
> > ($r->status) is creates a &qu
The status 400 (with $r->status_line) produces the same result "HTTP/1.1 200
OK" and with ($r->status) is creates a "HTTP/1.1 400 Bad Request" (the
custom string gets lost)
The $r->status with a code of 499 produces a "HTTP/1.1 400 Bad Request"
On Tue, Sep 28, 2010 at 6:31 AM, William A. Rowe J
Oops - seems I didn't include the group on my reply
FYI
Here is another test I did (simpler)
Apache Config
PerlModule FNBC::test_statusline
PerlWarn On
SetHandler perl-script
PerlResponseHandler FNBC::test_statusline
Hi - don't know if anybody else have come across this.
I have a mod_perl instance that produces output just as it should (checked
in the logs and I even written the output to file just to have an extra
check).
The tcpdump also show everything is ok.
BUT
The content has the following HTML append
Hi - I have a problem which I can't seem to solve.
I am busy implementing a webdav solution in mod_perl and as you may
know, the output is XML based.
The problem is that the output generated by mod_perl contains
additional characters before and after the XML which the webdav
clients don't seem to
