Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Prohibiting SSE via POST breaks `graphql-sse` usage (since 1.11.0)
See original GitHub issueSince v1.11.0 text/event-stream / SSE requests are forbidden via POST:
POST requests that try to execute Subscription operations will now receive an error and 405 status code. This is not considered a breaking change as SSE is not doable over POST by the specification and was never officially supported.
In helix-flare tests we are using graphql-sse to create a subscription connection. It seems, that graphql-sse uses POST and body to instantiate a connection which is now refused by graphql-helix.
Tests are running fine for helix-flare with graphql-helix@1.10.3 but are failing for 1.11.0.
Am I wrong here by assuming that this should actually work fine with POST requests, or should I choose a different approach?
Issue Analytics
- State:
- Created 2 years ago
- Comments:6 (3 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
@dan-lee @kefniark PR welcome for lifting the constraint 😇 Sorry for causing the troubles, we discussed it internally ans we dont see why we should not allow it for now, as the official spec is still pretty vague (aka non-existing 😅)!
Slightly related: I would also appreciate any comments and thoughs on https://github.com/graphql/graphql-over-http/issues/167
Fixed in
v1.12.0