Brian, Have you tried checking the log messages via `heroku logs` after getting a hanging request like this? That might help you shed some light on this. I personally have not seen an issue like this on any of the apps I've deployed though.
//Andrew Brian M wrote: > Hi, > > I currently have one dyno for my new app. I have read the doc and I > understand that the dyno will be unloaded after a short time. That's > perfectly understandable for a free app. > > The problem is that after my dyno has been unloaded, the first request > always times out. It never succeeds. > > To be more specific: the browser never gets a response. I am not > getting a 502 or any other HTTP status back. > > I can tell that the first request is successfully loading the app > because if I give up waiting and hit Refresh in the browser, the page > loads quickly. The problem is the first request never responded. > > I'm concerned that crawlers will never index me because they'll never > try "hitting refresh." > > I've read Heroku's "Error Pages" and "Peformance" and FAQ pages but > haven't found anything that would tell me I'm doing something wrong. > This is a simple app. It's not going into a long loop or doing > anything with heavy computation or calling an external web service > while handling a request. > > The Heroku FAQ under "What is dyno idling?" says "When a request comes > in to an idled app your dyno will be spun back up, causing a delay for > this first request." How long is the delay? I've tried waiting more > than a minute and still got no response. > > Thanks. > > Brian -- You received this message because you are subscribed to the Google Groups "Heroku" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/heroku?hl=en.
