Fix synchronous HEAD request #3187
Closed
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
When making a HEAD requests the response does not contain a ContentType. The Async version of `Request` already has this check, however the synchronous call fails with a NullReferenceException.
Contributor
Author
|
The build seems to have been stalled. How can I trigger a new build? From the logs: "No output has been received in the last 10m0s, this potentially indicates a stalled build or something wrong with the build itself." |
Contributor
|
@VanHuychemG Is this PR now superceded by #3188? |
Contributor
Author
|
@russcam Indeed, you can ignore this one. |
Contributor
|
Thanks @VanHuychemG. Closing this PR |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
When making a HEAD requests the response does not contain a ContentType. The Async version of
Requestalready has this check, however the synchronous call fails with a NullReferenceException.