Uploaded image for project: 'Undertow'
  1. Undertow
  2. UNDERTOW-1653

Different timeouts per HttpHandler or disable them for WebSockets

    Details

    • Type: Feature Request
    • Status: Open (View Workflow)
    • Priority: Major
    • Resolution: Unresolved
    • Affects Version/s: 2.0.29.Final
    • Fix Version/s: 2.2.0.Final
    • Component/s: API, Core, Servlet
    • Labels:
      None

      Description

      I'm using a WebSocket server and a normal HTTP server on the same port, and I want to set READ and WRITE_TIMEOUT for the HTTP server to prevent stuck clients.

      If I set the options using setSocketOption on the Undertow Server instance, it's applied for WebSockets too, and all WebSockets connections are closed after the WRITE_TIMEOUT time, making the WebSockets server unusable.

      Is there a way to either use different timeout settings for both paths on the same port, or disable timeout for WebSocket connections?

      Thanks

        Gliffy Diagrams

          Attachments

            Activity

              People

              • Assignee:
                flavia.rainone Flavia Rainone
                Reporter:
                soylomass Federico Mouse
              • Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                Dates

                • Created:
                  Updated: