On Wed, Mar 05, 2003 at 07:44:03PM -0800, Greg Stein wrote:
>
> If you capture the network packets in the above example, you'll see that an
> error message body is generated by mod_dav. The lines that are logged to
> error_log describe it all, and note that it is a 404 error.
>
> *However*, it seems that Apache is ignoring the 404 and/or replacing it with
> a 200 in the response status line. The client gets the 200 and starts to
> parse it, as if it were a proper report response. The DAV:error element at
> the root of the response is flagged as an error (that you're seeing). What
> *should* have happened is that the 404 comes back, and the error parser is
> invoked in ra_dav/util.c. That would properly handle the error.
i got a 500 error in my apache logs:
[Wed Mar 05 20:33:54 2003] [error] [client 66.93.78.194] A failure occurred during the completion and response generation for the update report. [500, #160016]
[Wed Mar 05 20:33:54 2003] [error] [client 66.93.78.194] (17)File exists: not_a_dir_error: invalid source parent directory '/test/foo' [500, #160016]
but otherwise i'm seeing exactly the same thing you are. the client got
a 200 response.
-brian
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu Mar 6 06:10:13 2003