These are chat archives for fanout/pushpin

16th
Apr 2018
Ben Leggett
@bleggett
Apr 16 2018 20:55
Maybe dumb question, I'm possibly missing something simple: Writing a little golang test server that is proxied by Pushpin. It sets Grip-Hold and Grip-Channel on the response, and returns a test message. However, I don't see the test message in the curl output until I push a second message to the same channel via pushpin-push
The test server definitely returns the response text, but it seems to get "stuck" in pushpin until I push a second message, at which point the original message and the second one are returned to the curl client. If I remove the Grip-* headers from the response, everything works as I expect.
Docs seem to indicate that Pushpin should return the initial server response to the client immediately.
Justin Karneges
@jkarneges
Apr 16 2018 22:02
hi @bleggett , double check this isn't a client-side buffering issue. for example, curl (due to running in a terminal) typically won't display data until a newline is received
so make sure your initial response ends with a newline, or use a different client to see the data
oh you can use -N with curl to disable buffering
Ben Leggett
@bleggett
Apr 16 2018 22:14
Oh geez, see I knew it was something goofy and simple. Thanks @jkarneges. Did not know curl had that behavior.
Justin Karneges
@jkarneges
Apr 16 2018 22:14
yeah it bites me every so often :)