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
{{ message }}
This repository was archived by the owner on May 6, 2026. It is now read-only.
Repository navigation
This repository was archived by the owner on May 6, 2026. It is now read-only.
Hapi: correctly extract url from request object #196
Thank you for opening this issue. On initial investigation, I agree that using req.url.pathname should be used if req.url is a URL object. Feel free to open a PR if you want to, but don't feel like you need to. We can take care of this too. Thanks.
I don't know typescript that well so not sure what as {} as string is doing so not sure what the quick fallback fix for this would be, thanks for picking this up!
Activity
DominicKramer commentedon Aug 27, 2018
Thank you for opening this issue. On initial investigation, I agree that using
req.url.pathnameshould be used ifreq.urlis a URL object. Feel free to open a PR if you want to, but don't feel like you need to. We can take care of this too. Thanks.AdriVanHoudt commentedon Aug 28, 2018
I don't know typescript that well so not sure what
as {} as stringis doing so not sure what the quick fallback fix for this would be, thanks for picking this up!fix: properly handle hapi v16+ req.url
fix: properly handle hapi v16+ req.url
fix: properly handle hapi v16+ req.url (#311)
fix: properly handle hapi v16+ req.url (#311)
fix: properly handle hapi v16+ req.url (#311)
fix: properly handle hapi v16+ req.url (#311)
fix: properly handle hapi v16+ req.url (#311)
fix: properly handle hapi v16+ req.url (#311)