You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
we have clients who cannot use graphql subscriptions when we use SSE. The endpoint just stays Pending in network tab of developer tools in browser.
Now I was able to reproduce this by using mitmproxy. mitmproxy does not support event-streams. I assume our clients will have the same issue.
I tried via distrinct and single connection of graphql-sse as described on docs
Did anyone stumble over this before? We are considering changing to websocket, but SSE seemed nicer.
It also seems to be difficult to have some fallback if subscriptions or specifically SSE or WS are not supported.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
Hi,
we have clients who cannot use graphql subscriptions when we use SSE. The endpoint just stays Pending in network tab of developer tools in browser.
Now I was able to reproduce this by using mitmproxy. mitmproxy does not support event-streams. I assume our clients will have the same issue.
I tried via distrinct and single connection of graphql-sse as described on docs
Did anyone stumble over this before? We are considering changing to websocket, but SSE seemed nicer.
It also seems to be difficult to have some fallback if subscriptions or specifically SSE or WS are not supported.
Kind regards
Beta Was this translation helpful? Give feedback.
All reactions