return correct content-types for swagger-ui files #17
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.
I was using the "Secure middleware" from echo together with echo-swagger. The result was a blank screen.
The option
X-Content-Type-Options: nosniff
complained, that the *.js files did not have the correctContent-Type
. Which is true as seen in the screenshot:they were delivered using
Content-Type: text/plain; charset=utf-8
I poked around and found that the gin-swagger implementation takes care of this (https://github.com/swaggo/gin-swagger/blob/master/swagger.go)
My PR just copies the logic of gin-swagger resulting in correct Content-Types which work with "nosniff"