Got error ---"EventSource's response has a MIME type ("text/html") that is not "text/event-stream". Aborting the connection."
See original GitHub issueHi, I got the following error in browser when using this middleware, any idea what it mean?
EventSource's response has a MIME type ("text/html") that is not "text/event-stream". Aborting the connection.
Issue Analytics
- State:
- Created 8 years ago
- Reactions:7
- Comments:14
Top Results From Across the Web
EventSource's response has a MIME type ("text/html") that is ...
This error occurs when your PHP code outputs text in the wrong format. This may be either a PHP error message (all of...
Read more >EventSource's response has a MIME type ("text/html") that is ...
I'm having this error on the console: EventSource's response has a MIME type (“text/html”) that is not “text/event-stream”. Aborting the ...
Read more >EventSource's response has a MIME type ("text ... - YouTrack
EventSource's response has a MIME type ("text/html") that is not "text/event-stream". Aborting the connection. What steps will reproduce the problem?
Read more >Using EventStream doesn't work because MimeType from ...
EventSource's response has a MIME type ("text/html") that is not "text/event-stream". Aborting the connection. Checking the URL (controller ...
Read more >[SSE Traditional Client] SSE Connection aborts - OutSystems
... following error in the browser console: "EventSource's response has a MIME type ("text/html") that is not "text/event-stream". Aborting the connection.
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
I also have this issue. My server setup looks like this:
EDIT:
I changed my config to this and it worked.
I had this error while serving a static index.html (using Express static middleware), and including my js bundle as a script there. As my first webpack entry, I had
'webpack-hot-middleware/client?path=http://localhost:3000/
It started working when I changed it to
'webpack-hot-middleware/client?path=http://localhost:3000/__webpack_hmr',