Invalid XML in PROPFINDs will trigger a generic 404 HTTP status

medabdellahi / google-caldav-issues

Automatically exported from code.google.com/p/google-caldav-issues

0 stars 0 forks source link

Invalid XML in PROPFINDs will trigger a generic 404 HTTP status #4

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago

What steps will reproduce the problem?
1. send a PROPFIND containing b0rked XML in the request entity

What is the expected output?

The best response is probably HTTP status 400 aka "Invalid Request".
Ideally the content of the response would contain the XML parsing error.

What do you see instead?

An 404 (Not Found) HTTP status. Which is very confusing since the resource
_does_ exist.

Original issue reported on code.google.com by helge.h...@googlemail.com on 31 Jul 2008 at 6:34

GoogleCodeExporter commented 9 years ago

Moreover the body of the response contains HTML code instead of XML DAV:error 
body.

Original comment by filip.na...@gmail.com on 4 Aug 2008 at 11:12