Handle missing Content-Type header in response. #24
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This defect was triggered by a server that replied to a request without a Content-Type header.
The response headers (as captured by wireshark) follow:
HTTP/1.1 302
Set-Cookie: JSESSIONID=E0DCDBB29FC3626D75D1B4876D4EBE86; Path=/derbytimer-0.1.4.BUILD-SNAPSHOT; HttpOnly
Location: /derbytimer-0.1.4.BUILD-SNAPSHOT/login;jsessionid=E0DCDBB29FC3626D75D1B4876D4EBE86?login_error=t
Content-Length: 0
Date: Sat, 30 Jun 2018 02:24:23 GMT