forked from villadora/express-http-proxy
-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Upgrade to 1.6.2-1 #1
Merged
Merged
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
…cific, functional steps, and more formal consistency between the lifecyle hooks. (villadora#170)
* [refactor] Adding comments. * [refactor] break sendProxy up slightly * [refactor] straitening up sendProxyReq method
…n forwardPathAsync (villadora#172)
* [refactor] working on decorateRequestWrapper * [refactor] incremental cleanup
…rify boundaries. Prep for standardizing workflow steps into thennables. (villadora#180) REMOVES decorateRequest, ADDS decorateReqOpt and decorateReqBody. This paves the way for pluggable bodyContent handlers, which has been a theme recently.
* extract resolveOptions to a module * extract_decorateRequestWrapper
* extract buildProxyRequest, give parsing host its own workflow step * Do not choose a random port number; causes test to fail when random number is already in use as a port number.
* Extract sendUserReq to module; other minor cleanup. * Expanding comment. * More comments. * Further comments. Improve property name. * Use lint approved form of loose equality
* Remove errant debuggers; fix timeout test * lint in subdirectories
* improve property name * extract decorateProxyReqBody to a module
…ts sequential to avoid issues with passed-by-reference 'container'. (villadora#198) Extract prepareProxyReq as a separate module
…ract copy headers from decorateUserRes. (villadora#200)
when the original is an empty string
I spent 2 days to find my issue. It was very hard to find the problem, but in some case, the body-parser change the body POST, and thn this body post is not sent to the target correctly. Hope it helps
lgtm. would do a diff with upstream as a quick sanity check after you merge |
Good point. To make sure, I just ran in this repo:
Diff output
Looks good! |
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.
Context in https://github.com/frontapp/front/pull/24480 and https://github.com/frontapp/front/pull/24496#discussion_r586373401.
TL;DR:
3-years-old issues addressed by our fork have been fixed (with other small bugs and way better error handling) on master so we could use
express-http-proxy
directly but there's a new issue (villadora#359) which makes GET requests to CloudFront/S3 fail because they have{}
as the body. We can use this PR villadora#457 on the original repo to fix it (by not parsing the body ifreq.method === 'GET'
) but it hasn't been merged yet and looking at the maintainer activity, I think it won't be merged in the next weeks. So I ended up taking the latest master and applying this PR as a patch in our fork.Steps done to upgrade + get patch from villadora#457:
git merge -X theirs villadora master
git merge v-electrolux master
package.json