Release v0.15.2 #128
Merged
Release v0.15.2 #128
Conversation
This file contains 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
thomasheartman
force-pushed
the
release/0.15.2
branch
from
b995223
to
09ca74c
Compare
thomasheartman
force-pushed
the
release/0.15.2
branch
from
09ca74c
to
f1a00a7
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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 PR releases v0.15.2. It contains a bugfix (#126) for the recently released content-type checking that the proxy does.
The content-type bug
Prior to this fix, the content-type checking would apply to all endpoints on the app you use for the proxy. If you use the proxy as a standalone app, then that doesn't really matter, but if you pass in a separate app, then all non-proxy endpoints will also have the content-type checking applied.
The fix, provided by @Dzixxx, makes it so that the content-type validation only happens on the endpoints bundled by the proxy.