Remove the dead websocket proxy route - #1
Merged
Merged
Conversation
Project events ride Server-Sent Events on the /data/ route now, so nothing calls /wsapps anymore. The connection-upgrade map goes with it — it was referenced nowhere, since both this route and /kibana hardcode their Connection headers. Kibana's own websocket handling is untouched. Completes the proxy half of protegeproject/webprotege-gwt-ui#308.
This was referenced Jul 28, 2026
Closed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The proxy half of protegeproject/webprotege-gwt-ui#308. Project events ride SSE on the existing
/data/route, and nothing has called/wsappssince the EventSource client shipped — the route is dead. Theconnection_upgrademap goes with it: it was referenced nowhere (both this route and/kibanahardcode their Connection headers). Kibana's own websocket handling is untouched.