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.

Sign up for GitHub

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

Jump to bottom

Override some HTTP statuses #11

Open
andreineculau opened this issue May 23, 2013 · 2 comments
Open

Override some HTTP statuses #11

andreineculau opened this issue May 23, 2013 · 2 comments
Labels
enhancement
Milestone
v5

Comments

@andreineculau
Copy link
Member

Some HTTP statuses may leak out information, so it's better to alter them.

While one can do so in override, maybe there should be a more specific way to override statuses just from the perspective of leaking out information.
@andreineculau
Copy link
Member Author

Example: 410 GONE instead of 404 NOT FOUND "leaks" out that there was indeed a resource at that URI, but not anymore. The latter may be preferred in some cases.

@andreineculau
Copy link
Member Author

FWIW most overrides would lead to an ambiguous 400 BAD REQUEST or 404 NOT FOUND

@mstade mstade mentioned this issue Apr 3, 2017
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement
Projects
None yet
Milestone
v5
Development

No branches or pull requests
1 participant
@andreineculau