I've solved the issue (I think it was the Connection-Length: -1 that was being objected to) but that does mean I can't post the output from it failing now, sorry.
I think it also works out that it was the campus router complaining (between my laptop and heroku) rather than heroku or the app. Sorry - the 502 had an uninformative "Via" header and I'd assumed the proxy was at heroku's end and forgotten about the one closer to my desk! Thanks very much for the swift response, though! On Wednesday, 17 April 2013 08:46:59 UTC+10, Blake Gentry wrote: > > Can you include an example curl for the app on Heroku when it receives a > 502? This would help verify whether the 502 response was sent by your app > or the Heroku router. > > Also, do your app's heroku logs show anything when this happens? > > On Monday, April 15, 2013 8:35:35 PM UTC-7, William Billingsley wrote: >> >> Is there a way to find out *what* Heroku's proxy objected to in a >> response? >> >> I have an app which on its Server Sent Events url gets a 502 Bad Gateway >> on Heroku (but for which its other urls work fine, and the app's own log >> messages suggest the app did try to respond) >> >> When I run the app on localhost, this is the output from cURL to the >> event stream, and I'm trying to work out if there's any part of this >> response that Heroku's proxy would object to, that would cause it to "502 >> Bad Gateway" on Heroku. >> >> $ curl -N -v http://localhost:9000/eventRoom/ssevents >> * About to connect() to localhost port 9000 (#0) >> * Trying ::1... >> * connected >> * Connected to localhost (::1) port 9000 (#0) >> > GET /eventRoom/ssevents HTTP/1.1 >> > User-Agent: curl/7.24.0 (x86_64-apple-darwin12.0) libcurl/7.24.0 >> OpenSSL/0.9.8r zlib/1.2.5 >> > Host: localhost:9000 >> > Accept: */* >> > >> < HTTP/1.1 200 OK >> < Connection: close >> * Negative content-length: -1, closing after transfer >> < Content-Length: -1 >> < Content-Type: text/event-stream >> < Set-Cookie: >> PLAY_SESSION=c115bf50b75969eeb9b9751b66f481829a1fd5c0-sessionkey%3A516cc2339acb3a6b00380eac; >> >> Path=/; HTTPOnly >> < >> data: {"type":"ignore"} >> >> data: {"type":"connected","listenerName":"516cc2339acb3a6b00380eab"} >> > -- -- You received this message because you are subscribed to the Google Groups "Heroku" group. 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_US?hl=en --- You received this message because you are subscribed to the Google Groups "Heroku Community" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
