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
Copy link
Copy link
Closed
Labels
🚨This issue needs some love.This issue needs some love.api: clouderrorreportingIssues related to the googleapis/nodejs-error-reporting API.Issues related to the googleapis/nodejs-error-reporting API.priority: p2Moderately-important priority. Fix may not be included in next release.Moderately-important priority. Fix may not be included in next release.type: bugError or flaw in code with unintended results or allowing sub-optimal usage patterns.Error or flaw in code with unintended results or allowing sub-optimal usage patterns.
Description
Activity
- addedtriage meI really want to be triaged.I really want to be triaged.🚨This issue needs some love.This issue needs some love.
on Aug 22, 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.- addedpriority: p2Moderately-important priority. Fix may not be included in next release.Moderately-important priority. Fix may not be included in next release.type: bugError or flaw in code with unintended results or allowing sub-optimal usage patterns.Error or flaw in code with unintended results or allowing sub-optimal usage patterns.and removed🚨This issue needs some love.This issue needs some love.triage meI really want to be triaged.I really want to be triaged.
on Aug 27, 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!- added 2 commits that reference this issue
on Feb 12, 2019 - added a commit that references this issue
on Feb 12, 2019 - addedapi: clouderrorreportingIssues related to the googleapis/nodejs-error-reporting API.Issues related to the googleapis/nodejs-error-reporting API.
on Jan 31, 2020 - added a commit that references this issue
on Feb 5, 2026
Metadata
Metadata
Assignees
Labels
🚨This issue needs some love.This issue needs some love.api: clouderrorreportingIssues related to the googleapis/nodejs-error-reporting API.Issues related to the googleapis/nodejs-error-reporting API.priority: p2Moderately-important priority. Fix may not be included in next release.Moderately-important priority. Fix may not be included in next release.type: bugError or flaw in code with unintended results or allowing sub-optimal usage patterns.Error or flaw in code with unintended results or allowing sub-optimal usage patterns.
If you are still having issues, please be sure to include as much information as
possible:
Environment details
Steps to reproduce
*
This is due to
nodejs-error-reporting/src/request-extractors/hapi.ts
Line 90 in 259f04d
req.urlcan be an URL object. I would suggest to fallback toreq.pathorreq.url.path.If that sounds ok I can do a PR if you'd like
Following these steps will guarantee the quickest resolution possible.
Thanks!