Maxime Petazzoni

Sounds like an interesting feature indeed. I'll try to get to it after the UDP tracker support (currently in progress in the announcing branch). Thanks for your interest in ttorrent!

I can't reproduce this issue in Firefox. Feel free to re-open along with a code sample if you're still having this problem 🙏🏻

Running behind a NAT might be an issue indeed. Can you run with debug logging enabled and give me that output?

`.stream()` isn't part of the original `EventSource` API. It's only in `sse.js` to make it easier to setup event listeners before starting the stream and avoid race conditions. But it's...

@karakostasi Can you share your code snippet on how you use SSE and configure the headers you're trying to send? The `sse.js` library doesn't do any transformation on the headers,...

@CocoaPriest Given your second comment, this seems like a backend-side issue. Note that you have to watch for response buffering/flushing on the server-side here. Are you sure your Express.js service...

Can you share what the browser devtools show for the request to `/api/process`? Any other difference between when it works (with `text/plain`) and when it doesn't (with `application/json`)?

I was fairly certain this isn't from anything `sse.js` is doing, but I built an example regardless to validate, and I can't reproduce this issue. Events come in normally. ![Screenshot...

Any particular reason you're faking a browser user agent instead of setting something more specific, like `User-Agent: ttorrent()` ? If the tracker is only checking for the presence of a...

Do you think you could provide a patch for a solution? I unfortunately don't have time to dive back into this code anymore.