`http: multiple response.WriteHeader calls` messages when used with `negroni` about eventsource HOT 4 CLOSED

Hi, first of all thanks for trying out the code and the bug report :-)

To answer your last question first, I haven't used this package with any other middleware systems. It looks like the Flush() here is causing your problem:

https://github.com/donovanhide/eventsource/blob/master/server.go#L78

which invokes:

https://github.com/golang/go/blob/2c12b81739ec2cb85073e125748fcbf5d2febb2c/src/net/http/server.go#L279

which writes the header :-) This is needed for eventsource streams which don't start broadcasting immediately (unlike your example code) so that the client can inspect the headers first and know that the response is in fact an event stream and the carry on waiting for some events to come later.

So, to solve your actual problem, you could avoid n.Run(...) and set up your own http.ListenAndServe() which has a router that sends some request paths to your SSE server and others to a Negroni set of handlers. I guess the question is whether you actually need some middleware functionality for your eventsource handler? If so, I guess this test needs beefing up as there may be some issue within negroni itself when handling flushes:

https://github.com/codegangsta/negroni/blob/c7477ad8e330bef55bf1ebe300cf8aa67c492d1b/response_writer_test.go#L144-L150

Let me know if you need more help!

from eventsource.

This looks like the easiest way to solve what you are doing:
https://github.com/codegangsta/negroni#route-specific-middleware

from eventsource.

Thanks @donovanhide !

I took some time to try and reproduce the bug but went short on going further.

Anyway, yes, the eventsource stream could benefit from the existing middlewares such as permissions, logger and so on.

I'll keep you in touch ;)

from eventsource.

Actually, there was a simple fix :-) See if it works for you now!

from eventsource.