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

Handle no-content response in DefaultHttpJsonRequest #5577

Merged
merged 1 commit into from
Jul 10, 2017

Conversation

dmytro-ndp
Copy link
Contributor

@dmytro-ndp dmytro-ndp commented Jul 10, 2017

What does this PR do?

This request fixes DefaultHttpJsonRequest class not to check Content Type of response if it has status code 204 "No Content".
It allows, for example, to avoid unexpected IOException "No content" in case of successful DELETE request with empty response.

Signed-off-by: Dmytro Nochevnov dnochevnov@codenvy.com

@evoevodin, @tolusha: please, review this request.

Signed-off-by: Dmytro Nochevnov <dnochevnov@codenvy.com>
@dmytro-ndp dmytro-ndp merged commit b108b50 into master Jul 10, 2017
@dmytro-ndp dmytro-ndp deleted the handle-no-content-response branch July 10, 2017 12:13
@codenvy-ci
Copy link

JPinkney pushed a commit to JPinkney/che that referenced this pull request Aug 17, 2017
Signed-off-by: Dmytro Nochevnov <dnochevnov@codenvy.com>
@dmytro-ndp dmytro-ndp restored the handle-no-content-response branch December 8, 2017 08:56
@dmytro-ndp dmytro-ndp deleted the handle-no-content-response branch December 8, 2017 09:00
This pull request was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants