Inquiry Regarding Server-Side Events and Traffic Inspection

Hi ​@john.gao ,

Thank you for posting your question, did you looked at this this documentation: Microsoft and Netskope SSE Coexistence - Netskope Knowledge Portal: https://docs.netskope.com/en/microsoft-and-netskope-sse-coexistence-1/

I would suggest reaching out to Netskope technical support  or your account SE for more detailed product documentation for accurate and up-to-date information on this topic.

​@john.gao, what behavior are you seeing? Netskope acts as a proxy so it’s terminating and opening connections on behalf of users and devices.  Have any of your joint customers opened a case with Netskope to provide additional information? 

 

​@sshiflett 

We have observed an issue where server-sent events (SSE) appear to be buffered by the proxy and are only flushed to the client when the connection is terminated by our backend server. Here’s an example to illustrate:

1. A user establishes an SSE connection to our backend server.

2. Your proxy is in between, handling the connection.

3. Our backend server sends multiple SSE events (e.g., SSE event 1, SSE event 2, SSE event 3, etc.).

4. However, instead of the user receiving these events in real-time as they are sent by the backend, all the events are delivered simultaneously only when the backend server closes the connection.

This behavior defeats the core purpose of SSE, which is to push real-time updates to a client over a single, long-lived HTTP connection. Based on this, we suspect that the proxy might be buffering the SSE events.

We have requested our customers to coordinate with their IT teams to address this issue. However, we are unsure whether they have raised a case with Netskope.

Thanks.

John

​@john.gao, 

That all makes sense.  We would likely need a support case to troubleshoot this.  If one of your customers does open a case, please let me know the case number so I can track it.  A HAR capture or packet capture when reproducing the issue would be a good starting point along with the Netskope client logs.