Skip to content

Conversation

@ealmloff
Copy link
Member

@ealmloff ealmloff commented May 12, 2025

The new logic to override different parts of the server function response broke the websocket server function protocol because it always set the response status to 200 by default. This PR fixes the issue by tracking what parts of the response have been written to and only writing those back to the final response

Fixes #4100

TODO:

  • Verify fix
  • Add a WebSocket playwright test

@ealmloff ealmloff added bug Something isn't working fullstack related to the fullstack crate labels May 12, 2025
@ealmloff ealmloff marked this pull request as ready for review May 13, 2025 01:04
@ealmloff ealmloff requested a review from a team as a code owner May 13, 2025 01:04
@ealmloff ealmloff changed the title Fix websocket server functions Fix websocket server functions and add an example May 13, 2025
@ealmloff ealmloff added the example Update examples label May 13, 2025
@jkelleyrtp jkelleyrtp merged commit 6b70ba7 into DioxusLabs:main May 14, 2025
16 of 17 checks passed
AnteDeliria pushed a commit to AnteDeliria/dioxus that referenced this pull request Jun 2, 2025
* Fix websocket server function

* Add websocket test

* add a websocket example

* fix clippy
AnteDeliria pushed a commit to AnteDeliria/dioxus that referenced this pull request Jul 23, 2025
* Fix websocket server function

* Add websocket test

* add a websocket example

* fix clippy
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

bug Something isn't working example Update examples fullstack related to the fullstack crate

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Websocket connection closed when using fullstack

2 participants