Bug: Error on Google Cloud Functions
See original GitHub issueWhen used on Google Cloud Functions an error is thrown due to req.originalURL === ""
. The error is thrown from these 3 lines handling originalPath
.
The debugging to find this bug can be found in this tweet thread with @blakeembrey
Issue Analytics
- State:
- Created 6 years ago
- Comments:17 (11 by maintainers)
Top Results From Across the Web
Troubleshooting Cloud Functions - Google Cloud
Function deployment fails while executing function's global scope. This error indicates that there was a problem with your code. The deployment pipeline ...
Read more >c# - Google Cloud Function Deployment Error "Function failed ...
Google Cloud Function Deployment Error "Function failed on loading user code. This is likely due to a bug in the user code.".
Read more >[BUG] Google Cloud Function error (deploy) #2321 - GitHub
I'm trying to deploy my playwright application in Google Cloud Functions. It seems like there is a problem to spawn the browser. Error: ......
Read more >[ Tracking Bug only ] GCP Serverless ( Cloud Functions ...
This bug is only meant to be a tracking bug to reduce the overall performance of this issue over time such that the...
Read more >hello custom training tutorial failed on cloud function deploy
This is likely due to a bug in the user code. Error message: Error: please examine your function logs to see the error...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Well, thinking about it, probably this would be the fix:
If no
pathname
, then callnext()
if the cookie path is set to anything other than'/'
(the default). Since/
would cover the entire domain anyway, checking the path is not useful. Otherwise, check the path andnext()
if not prefixing.Publishing to npm as version 1.15.5