Skip to content
This repository was archived by the owner on Feb 24, 2024. It is now read-only.

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
@cyrusdaboo
Labels
Other P2: Expected Task
Milestone
Later

Comments

@macosforgebot
Copy link

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

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

  • Radar deleted
  • Priority changed from 5: Not set to 2: Expected

@macosforgebot
Copy link
Author

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

  • Milestone set to Later

@macosforgebot macosforgebot added this to the Later milestone Aug 4, 2016
@mocomoc mocomoc assigned wsanchez and cyrusdaboo and unassigned wsanchez Aug 4, 2016
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@cyrusdaboo cyrusdaboo

Labels
Other P2: Expected Task
Projects
None yet
Milestone
Later
Development

No branches or pull requests
3 participants
@wsanchez @cyrusdaboo @macosforgebot