These are chat archives for fanout/pushpin

Aug 2015
Aug 30 2015 10:09 UTC
so far it seems like that the stream has correct headers
But atleast publishing to that channel, doesn't seem to work.
Or atleast the javascript stream wont receive it.
Aug 30 2015 11:04 UTC

curl -i -v -H "Accept: text/event-stream" http://localhost:8000/my/request/url/

  • Trying ::1...
  • connect to ::1 port 8000 failed: Connection refused
  • Trying
  • Connected to localhost ( port 8000 (#0)

    GET /my/request/url/ HTTP/1.1
    Host: localhost:8000
    User-Agent: curl/7.43.0
    Accept: text/event-stream

  • HTTP 1.0, assume close after body
    < HTTP/1.0 200 OK
    HTTP/1.0 200 OK
    < Date: Sun, 30 Aug 2015 11:03:47 GMT
    Date: Sun, 30 Aug 2015 11:03:47 GMT
    < Server: WSGIServer/0.2 CPython/3.4.3
    Server: WSGIServer/0.2 CPython/3.4.3
    < Content-Type: text/event-stream
    Content-Type: text/event-stream
    < X-Frame-Options: SAMEORIGIN
    X-Frame-Options: SAMEORIGIN
    < Grip-Channel: mychannel
    Grip-Channel: mychannel
    < Grip-Hold: stream
    Grip-Hold: stream

Stream opened, prepare yourself!

  • Closing connection 0
Trying it with port 7999 gives bad gateway :p
Aug 30 2015 13:05 UTC
Seems to be a port problem. I think.
Justin Karneges
Aug 30 2015 18:56 UTC
that's a request to the backend server, right? looks good to me
edit pushpin's routes file to contain a line like this:
* localhost:8000
by default it routes to port 80, and you probably have nothing running there, hence the error
with the correct route in place, you should be able to connect to port 7999
Aug 30 2015 19:56 UTC
Ah, ofc. I need to test that when I get my laptop.
Aug 30 2015 23:54 UTC
Hmm, shouldn't the request keep connection up? When I look at your php example it does, but for me it closes it immediately with "Closing connection 0". Changing port to 8000 doesn't seem to change anything.
8000 is the same port that django uses for python runserver.