Class AbstractHandshakeHandler

  • java.lang.Object
    • Field Detail

      • logger

        protected final Log logger
    • Constructor Detail

      • AbstractHandshakeHandler

        protected AbstractHandshakeHandler()
        Default constructor that auto-detects and instantiates a RequestUpgradeStrategy suitable for the runtime container.
        java.lang.IllegalStateException - if no RequestUpgradeStrategy can be found.
      • AbstractHandshakeHandler

        protected AbstractHandshakeHandler(RequestUpgradeStrategy requestUpgradeStrategy)
        A constructor that accepts a runtime-specific RequestUpgradeStrategy.
        requestUpgradeStrategy - the upgrade strategy to use
    • Method Detail

      • setSupportedProtocols

        public void setSupportedProtocols(java.lang.String... protocols)
        Use this property to configure the list of supported sub-protocols. The first configured sub-protocol that matches a client-requested sub-protocol is accepted. If there are no matches the response will not contain a Sec-WebSocket-Protocol header.

        Note that if the WebSocketHandler passed in at runtime is an instance of SubProtocolCapable then there is not need to explicitly configure this property. That is certainly the case with the built-in STOMP over WebSocket support. Therefore this property should be configured explicitly only if the WebSocketHandler does not implement SubProtocolCapable.

      • getSupportedProtocols

        public java.lang.String[] getSupportedProtocols()
        Return the list of supported sub-protocols.
      • start

        public void start()
        Description copied from interface: Lifecycle
        Start this component.

        Should not throw an exception if the component is already running.

        In the case of a container, this will propagate the start signal to all components that apply.

        Specified by:
        start in interface Lifecycle
        See Also:
      • doStart

        protected void doStart()
      • stop

        public void stop()
        Description copied from interface: Lifecycle
        Stop this component, typically in a synchronous fashion, such that the component is fully stopped upon return of this method. Consider implementing SmartLifecycle and its stop(Runnable) variant when asynchronous stop behavior is necessary.

        Note that this stop notification is not guaranteed to come before destruction: On regular shutdown, Lifecycle beans will first receive a stop notification before the general destruction callbacks are being propagated; however, on hot refresh during a context's lifetime or on aborted refresh attempts, a given bean's destroy method will be called without any consideration of stop signals upfront.

        Should not throw an exception if the component is not running (not started yet).

        In the case of a container, this will propagate the stop signal to all components that apply.

        Specified by:
        stop in interface Lifecycle
        See Also:
        SmartLifecycle.stop(Runnable), DisposableBean.destroy()
      • doStop

        protected void doStop()
      • isRunning

        public boolean isRunning()
        Description copied from interface: Lifecycle
        Check whether this component is currently running.

        In the case of a container, this will return true only if all components that apply are currently running.

        Specified by:
        isRunning in interface Lifecycle
        whether the component is currently running
      • doHandshake

        public final boolean doHandshake(ServerHttpRequest request,
                                         ServerHttpResponse response,
                                         WebSocketHandler wsHandler,
                                         java.util.Map<java.lang.String,java.lang.Object> attributes)
                                  throws HandshakeFailureException
        Description copied from interface: HandshakeHandler
        Initiate the handshake.
        Specified by:
        doHandshake in interface HandshakeHandler
        request - the current request
        response - the current response
        wsHandler - the handler to process WebSocket messages; see PerConnectionWebSocketHandler for providing a handler with per-connection lifecycle.
        attributes - attributes from the HTTP handshake to associate with the WebSocket session; the provided attributes are copied, the original map is not used.
        whether the handshake negotiation was successful or not. In either case the response status, headers, and body will have been updated to reflect the result of the negotiation
        HandshakeFailureException - thrown when handshake processing failed to complete due to an internal, unrecoverable error, i.e. a server error as opposed to a failure to successfully negotiate the handshake.
      • handleInvalidUpgradeHeader

        protected void handleInvalidUpgradeHeader(ServerHttpRequest request,
                                                  ServerHttpResponse response)
      • handleInvalidConnectHeader

        protected void handleInvalidConnectHeader(ServerHttpRequest request,
                                                  ServerHttpResponse response)
      • isWebSocketVersionSupported

        protected boolean isWebSocketVersionSupported(WebSocketHttpHeaders httpHeaders)
      • getSupportedVersions

        protected java.lang.String[] getSupportedVersions()
      • isValidOrigin

        protected boolean isValidOrigin(ServerHttpRequest request)
        Return whether the request Origin header value is valid or not. By default, all origins as considered as valid. Consider using an OriginHandshakeInterceptor for filtering origins if needed.
      • selectProtocol

        protected java.lang.String selectProtocol(java.util.List<java.lang.String> requestedProtocols,
                                                            WebSocketHandler webSocketHandler)
        Perform the sub-protocol negotiation based on requested and supported sub-protocols. For the list of supported sub-protocols, this method first checks if the target WebSocketHandler is a SubProtocolCapable and then also checks if any sub-protocols have been explicitly configured with setSupportedProtocols(String...).
        requestedProtocols - the requested sub-protocols
        webSocketHandler - the WebSocketHandler that will be used
        the selected protocols or null
        See Also:
      • determineHandlerSupportedProtocols

        protected final java.util.List<java.lang.String> determineHandlerSupportedProtocols(WebSocketHandler handler)
        Determine the sub-protocols supported by the given WebSocketHandler by checking whether it is an instance of SubProtocolCapable.
        handler - the handler to check
        a list of supported protocols, or an empty list if none available
      • filterRequestedExtensions

        protected java.util.List<WebSocketExtension> filterRequestedExtensions(ServerHttpRequest request,
                                                                               java.util.List<WebSocketExtension> requestedExtensions,
                                                                               java.util.List<WebSocketExtension> supportedExtensions)
        Filter the list of requested WebSocket extensions.

        As of 4.1, the default implementation of this method filters the list to leave only extensions that are both requested and supported.

        request - the current request
        requestedExtensions - the list of extensions requested by the client
        supportedExtensions - the list of extensions supported by the server
        the selected extensions or an empty list
      • determineUser

        protected determineUser(ServerHttpRequest request,
                                                                  WebSocketHandler wsHandler,
                                                                  java.util.Map<java.lang.String,java.lang.Object> attributes)
        A method that can be used to associate a user with the WebSocket session in the process of being established. The default implementation calls ServerHttpRequest.getPrincipal()

        Subclasses can provide custom logic for associating a user with a session, for example for assigning a name to anonymous users (i.e. not fully authenticated).

        request - the handshake request
        wsHandler - the WebSocket handler that will handle messages
        attributes - handshake attributes to pass to the WebSocket session
        the user for the WebSocket session, or null if not available