Skip to content
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

fix: --custom-header flag implementation #242

Merged
merged 2 commits into from
Jul 4, 2020

Conversation

consideRatio
Copy link
Member

The --custom-header flag added in #206 didn't seem to work, this PR attempts to fix this and also adds a test to make sure.

Given current node-http-server, the key fixes are:

  • A singular/plural typo for customHeader(s)
  • node-http-proxy configuration API, it now needs to be headers and not customHeaders
  • headers now needs to get an object, not a list of objects

Closes #223.

@consideRatio
Copy link
Member Author

@minrk I think this is ready for merge

@consideRatio
Copy link
Member Author

consideRatio commented Jul 2, 2020

@minrk as the current implementation isn't working, and I've verified this implementation works with tests. I'll go ahead and self-merge this tomorrow.

@consideRatio
Copy link
Member Author

I did a another self review of my code and became more confident the implementation to fix the current broken logic makes sense. I'll go ahead and self-merge this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

The --custom-header doesn't do anything
2 participants