Skip to content
This repository has been archived by the owner on Apr 10, 2019. It is now read-only.

The server error responses should have different content type then text/html #128

Open
slavaschmidt opened this issue May 6, 2016 · 1 comment
Open

The server error responses should have different content type then text/html #128

slavaschmidt opened this issue May 6, 2016 · 1 comment

Comments

@slavaschmidt
Copy link
Contributor

Usually, REST APIs use application/json or more specific formats. Therefore there is no text/html defined as supported format for error codes. Thus, failing test cases are not delivering correct information about the cause of the failure
slavaschmidt added a commit that referenced this issue May 7, 2016
@slavaschmidt
#128, fix: Additional asserion for multipleOf validation
ffc6da5
slavaschmidt added a commit that referenced this issue May 7, 2016
@slavaschmidt
#128, fix: Additional asserion for multipleOf validation
8f5d515
slavaschmidt added a commit that referenced this issue May 7, 2016
@slavaschmidt
#128, fix: Additional check for content type presence
b4a5221
@slavaschmidt
Copy link
Contributor Author

Seems that the solution would be a custom ErrorHanler like this
In this case the fix must be implemented in activator template

slavaschmidt added a commit that referenced this issue May 7, 2016
@slavaschmidt
Merge pull request #131 from zalando/#128_Content_type_for_server_errors
82e2f22 
#128 content type for server errors
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@slavaschmidt