Viktor comments

Results 161 comments of


Viktor

who know how use in android client？

Can I close this?

EventSource's response has a MIME type ("text/html") that is not "text/event-stream". Aborting the connection.

What do you see if you open that URL in your browser?

EventSource's response has a MIME type ("text/html") that is not "text/event-stream". Aborting the connection.

@lmkoushik , @abzfarah , @Jurigag , are you sure the response is correct?

.close() does not abort current event source fetch connections

Why? `reader.cancel()` is used to cancel the request. Doesn't it abort the connection? Of course, it will not work unless the connection gets the "reading state", but it is not...

.close() does not abort current event source fetch connections

It seems, the `reader.cancel()` does not close the connection in Edge.

.close() does not abort current event source fetch connections

`AbortController` also doesn't help.

.close() does not abort current event source fetch connections

try to use the `Transport` option: ``` var es = new EventSource(url, { Transport: XMLHttpRequest }); ``` I see no solutions with `Fetch API`.

.close() does not abort current event source fetch connections

https://github.com/Yaffle/EventSource/commit/fd5408ef717b4679c186c80644dd46226176f03d - I have tried to use the suggested changes.

.close() does not abort current event source fetch connections

@svyotov , does it work? I have no Edge 18, but it does it work in Edge 17.

.close() does not abort current event source fetch connections

I have tested Edge 18 - it is still doesn't close connection when calling `EventSource#close` with any AbortController or Reader#cancel