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.
A couple of bugfixes. First of all I've had situations where
Content-Type
header contained an encoding specification. This ignores it. A couple of other changes in the first patch also seemed necessary. (I was working on top of an older version, not master).The second patch is because the HTTP request raises an exception if the result is 404, but this is the natural result from non-existing files. The result was that simply calling
haskey
throws and exception when the result should be false. I'm not sure how to prevent HTTP.jl to simple return a 404 result without throwing an exception. This patches make things work, ignoring theHTTP.ExceptionRequest.StatusError
exception.