Lookup route during OPTIONS by using request.info.hostname. Closes #2930#2931
Merged
hueniverse merged 1 commit intohapijs:masterfrom Nov 5, 2015
Merged
Conversation
Member
|
Thanks for tracking this down– looks good to me. |
hueniverse
added a commit
that referenced
this pull request
Nov 5, 2015
Lookup route during OPTIONS by using request.info.hostname. Closes #2930
|
This thread has been automatically locked due to inactivity. Please open a new issue for related bugs or questions following the new issue template instructions. |
This file contains hidden or 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
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.
During a normal request the route is looked up using the value of
request.info.hostname:However during an OPTIONS request, it's currently being looked up via the value of
request.headers.host:These values are different when not using port 80, therfore this can cause the route not to be found correctly when there's a vhost setting on a route as per hapijs/glue#38 #2930.