Hello
I still have no clue. I tend to think EventSource simply "works" like that,
that is triggering the onerror handler (if you have set-up one) after a
response gets delivered. (Even a 200-status response.) And one simply has
to decide how to deal with such pseudo-error. If the readyState of you
Root cause?
> On Feb 28, 2015, at 15:20, Jaroslav Záruba wrote:
>
> Hello again :)
>
> Apparently adding Connection: close" header to my response prevents the
> "evil" heaqder to be added.
> And it turns out the header isn't the reason why EventSource receives the
> message-less error.
>
> Ch
Hello again :)
Apparently adding Connection: close" header to my response prevents the
"evil" heaqder to be added.
And it turns out the header isn't the reason why EventSource receives the
message-less error.
Cheers
Jarda
On Sat, Feb 28, 2015 at 9:54 PM, Jaroslav Záruba
wrote:
> Hello
>
> I'
Hello
I'm trying to set-up an EventSource servlet, yet Tomcat seems to be adding
"Transfer-Encoding: chunked" header to my responses, so they trigger the
onerror handler on my EventSource object.
According to some, setting org.apache.coyote.http11.Http11NioProtocol as
the protocol on my http sho
