Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Allow 400 (Bad Request) for bad requests #12

Open
macosforgebot opened this issue Jul 26, 2010 · 2 comments
Open

Allow 400 (Bad Request) for bad requests #12

macosforgebot opened this issue Jul 26, 2010 · 2 comments
Assignees
Milestone

Comments

@macosforgebot
Copy link

@macosforgebot macosforgebot commented Jul 26, 2010

douglm@… originally submitted this as ticket:389


Validator prepostcondition only allows 403, 409, 507 as a status even though 400 seems valid and sometimes more appropriate (e..g non-UTC datetime in time-range):

DAV says

Servers MAY reject questionable requests (even though
   they consist of well-formed XML), for instance, with a 400 (Bad
   Request) status code and an optional response body explaining the
   problem.
@macosforgebot
Copy link
Author

@macosforgebot macosforgebot commented Aug 1, 2011

@wsanchez originally submitted this as comment:1:⁠ticket:389

  • Radar deleted
  • Priority changed from 5: Not set to 2: Expected
@macosforgebot
Copy link
Author

@macosforgebot macosforgebot commented Nov 30, 2011

@wsanchez originally submitted this as comment:2:⁠ticket:389

  • Milestone set to Later
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
3 participants
You can’t perform that action at this time.