This repository has been archived by the owner on Jan 29, 2020. It is now read-only.
Add custom HTTP headers to ie_com listener #836
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
|
@leoloobeek thanks for this. Tested the listener out and everything seems to be working as it should. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Enhances the "ie_com" listener to be able to use custom HTTP headers similar to the "http" listener. Also added the option for end user to choose which HTTP header will contain the routing cookie, in the past it was "CF-RAY". Users can now choose a custom HTTP request header to store the routing cookie, but "CF-RAY" is still the default.
The intent of these changes is to allow domain fronting for the "ie_com" listener.