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

add location setting similar to old hapi server location #85

Merged
merged 4 commits into from
May 4, 2015

Conversation

brand7n
Copy link
Contributor

@brand7n brand7n commented May 4, 2015

The forceHttps option is not sufficient to cover every configuration. For example the port visible to the user's browser may be different than the port inferred by the Hapi server. In fact, the host may also be different if there is a load balancer involved. This PR attempts to restore the flexibility available when bell referenced the Hapi server location setting.

@jplock
Copy link

jplock commented May 4, 2015

+1

2 similar comments
@darthberen
Copy link

+1

@eruizdechavez
Copy link

+1

@geek geek added the feature New functionality or improvement label May 4, 2015
@geek geek added this to the 2.6.1 milestone May 4, 2015
@geek geek self-assigned this May 4, 2015
@geek
Copy link
Member

geek commented May 4, 2015

@brand7n well done, this looks great :)

geek added a commit that referenced this pull request May 4, 2015
add location setting similar to old hapi server location
@geek geek merged commit f8875ca into hapijs:master May 4, 2015
@brand7n
Copy link
Contributor Author

brand7n commented May 4, 2015

@geek awesome...thanks!!

@lock
Copy link

lock bot commented Jan 9, 2020

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.

@lock lock bot locked as resolved and limited conversation to collaborators Jan 9, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
feature New functionality or improvement
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants