-
-
Notifications
You must be signed in to change notification settings - Fork 4.8k
Request closed without response #1896
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
By examining the logs I've realised that this code is actually catching Heroku H27 and H28 errors, which explains the 55 seconds timeout for the H28's: https://devcenter.heroku.com/articles/http-routing#timeouts. Going back to the drawing board on this one. |
Thanks for the update. Let me know if you find anything we can help with. |
Digging a bit deeper, a typical log looks like the following: This looks like the client is trying to make a connect request, which is not supported by Heroku. Could this be coming from a client SDK or internal parse-server request? |
I'm not familiar enough with all of our SDKs to say. It could also be a random crawler on the web, or someone probing your app for vulnerabilities. |
Any more news on this? I'm seeing this log when I'm calling a cloud function from the iOS SDK to send a push notification - I'm also using Heroku |
Issue Description
We're seeing Heroku error reports of requests being closed with no response aka H13. https://devcenter.heroku.com/articles/error-codes#h13-connection-closed-without-response
To try and track down the issue I added some debug logging to my index.js
Logs/Trace
I don't have any more info yet but could the client be sending the body as compressed? It seems there is some content due to the content-length but body is displayed as empty.
All of the errors of this type have a duration of ~55s
Environment Setup
The text was updated successfully, but these errors were encountered: