Output yml/yaml as text/plain through nginX in docker container #7749
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.
Description
Added type
text/plain
foryml
andyaml
indocker/nginx.conf
.Motivation and Context
Ref #6019 (not sure if this covers all the problems mentioned there). When you did specify a
*.y(a)ml
file for theconfigUrl
this was not working with the provided docker image. The reason seems to be that the bundled nginX has no MIME type entry for YAML and so outputs this asapplication/octet-stream
. That caused the config not to load. Addingtext/plain
types for*.y(a)ml
seems to have fixed the problem.How Has This Been Tested?
Build a docker image locally and tested if it worked with the provided
swagger-config.yaml
file.Screenshots (if appropriate):
Checklist
My PR contains...
src/
is unmodified: changes to documentation, CI, metadata, etc.)package.json
)My changes...
Documentation
Automated tests