Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Adds support for users to control the outcome of a WebSocket upgrade request #8594

Merged
merged 2 commits into from
Apr 3, 2024
Merged

Adds support for users to control the outcome of a WebSocket upgrade request #8594

merged 2 commits into from
Apr 3, 2024

Commits on Apr 1, 2024

  1. Adds support for users to control the outcome of a WebSocket upgrade … 

    …request. If the user handler returns a non-101 code, the protocol upgrade fails and a response is written back based on the data returned by the handler, including the error code, headers and the reason for the failure. See issue 7953. Some new tests.
    @spericas
    spericas committed Apr 1, 2024
    Configuration menu
    Copy the full SHA
    f0fc904 View commit details
    Browse the repository at this point in the history

Commits on Apr 2, 2024

  1. Removes all possible upgrade headers that don't belong in a failed re… 

    …sponse. Some other minor cleanup.

Signed-off-by: Santiago Pericas-Geertsen <santiago.pericasgeertsen@oracle.com>
    @spericas
    spericas committed Apr 2, 2024
    Configuration menu
    Copy the full SHA
    c3ee959 View commit details
    Browse the repository at this point in the history