You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm using express vhost behind a reverse proxy and i want to use this module based on the x-forwarded-host header as opposed to the host header that is hardcoded here:
EDIT:
I've just re-read the readme again and this would be the only part of this module which adds a direct express dependency. Maybe the code could be:
var host = req.hostname || req.host || req.headers.host
To support express 3/4 and connect servers.
The text was updated successfully, but these errors were encountered:
…ixesexpressjs#20
This is so that the module works when express has `trust proxy` enabled
and the `Host` header is expected to come from `X-Forwarded-Host`
I'm using express vhost behind a reverse proxy and i want to use this module based on the
x-forwarded-host
header as opposed to thehost
header that is hardcoded here:vhost/index.js
Line 77 in 12565d1
Express 4 supports this by accessing
req.hostname
directly: http://expressjs.com/en/4x/api.html#req.hostnameExpress 3 supports this at
req.host
:http://expressjs.com/en/3x/api.html#req.host
Is this module still intended to support express v3? Would you accept a pull request that replaces:
vhost/index.js
Line 77 in 12565d1
with:
to keep support with both express v3 and v4.
EDIT:
I've just re-read the readme again and this would be the only part of this module which adds a direct express dependency. Maybe the code could be:
To support express 3/4 and connect servers.
The text was updated successfully, but these errors were encountered: