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
A route does have a vhost option that can restrict the route to an individual host or an array of hosts. There are also a few examples of using it in the router tests.
Ok, so one tiny little thing. The vhost is matched based on request.raw.req.headers.host, which ends up being hostname:port in router.js:route(request). Which is kind of inconvenient because you typically don't associate the port with the path or even the virtual host. The workaround I have in place is to just add ":PORT" to the end of the vhost when I set the route, but it would nice if hapi could just associate the path regardless of the port. Otherwise, it works great. Thanks.
Is there support for virtual hosts? With connect, we were able to support virtual hosts by implementing our own routes. Thanks.
The text was updated successfully, but these errors were encountered: