spring-websocket

问题 We are attempting to use a combination of spring session, spring security and websockets to implement security for a websocket API without using cookies. Ideally we would be using a authorization header or authentication using the websocket/stomp messages but this does not seem to be possible with the current spring websocket support. We are using a pre-auth provider to validate a query parameter token and log the user in. I can see that the proper user is pulled out in the pre-auth for the

问题 I'm writing a test application using web sockets. Sometimes after a re-connection, Spring Boot v1.5.10.RELEASE does not find a session associated with the user. This problem not reproducible constantly. Test: @Test public void receiveInCycle() throws Exception { for (int i = 0; i < 9999; i++) { receive(); } } public void receive() throws Exception { Collection<Object> payloads = new ArrayList<>(); //create session for "kate" user StompSession stompSession = createStompSession("kate");

问题 I am going through Spring 4 websocket + stomp + rabbitmq(RabbitMQ-Web-Stomp plugin) architecture and I have a question about clustering. As per my understanding here Spring MVC act as a gateway for STOMP requests. If we cluster the application instance with spring web socket configuration will it create any confusion? For an example will it open multiple listeners and how will in such a case this architecture behave? 回答1: In this scenario, you would need to use load balancing and a message

问题 Summary I would like to implement websocket communication over STOMP. Authenticate The user in the time of the first (HTTP request) websocket handshake and use this Principal for authorizing websocket messages later. Problem The system authenticates the client at the first time when it tries to connect to the websocket endpoint (the time of HTTP handshake). My spring security filter and Authentication provider does its job and authenticates the client properly. After this I can check that the

问题 So I'm looking to upgrade my projects from spring boot 1.1.9.RELEASE to 1.2.1.RELEASE. <dependency> <groupId>org.springframework.boot</groupId> <artifactId>spring-boot-starter-websocket</artifactId> <version>${spring.boot.version}</version> </dependency> However, on startup, I gained: Exception in thread "Thread-0" org.springframework.context.ApplicationContextException: Failed to start bean 'subProtocolWebSocketHandler'; nested exception is java.lang.IllegalArgumentException: No handlers at

问题 I have a Spring Websocket Stomp application that accepts SUBSCRIBE requests. In application I have a handler for SUBSCRIBE, that is, @Component public class SubscribeStompEventHandler implements ApplicationListener<SessionSubscribeEvent> { @Override public void onApplicationEvent(SessionSubscribeEvent event) {} } that I use to validate subscription. I would check something in the onApplicationEvent and send STOMP ERROR message back to client from this function. I found this recipe How to send

问题 I'm trying to configure WebSocket via Spring with STOMP, OAuth 2 and SockJS. New spec tells us how to implement it using Interceptors. The case is: if user is authenticated there is an Bearer Token in Native header of CONNECT request and there is no problem to set principal via Token. But my task is to use BrowserToken for unauthorized users (which is saved in Cookies). How can i get it from the request? 回答1: I've found a solution: @Override public void registerStompEndpoints

问题 I am testing the server with spring-boot. However, I got some problems during doing test. my test is How many memories server use with increasing the web socket sessions(the number of client). 1,000 clients(lesser than 9000 sessions) has no issues with doing the test. but, When I tried to test 10k connections, server made connections almost until 10,000.(sometimes creating sessions until 9990, sometimes 9988, 9996 like this, not the specific limit the number of socket) after that, it just

问题 I'm new to spring websocket. I want to send product changes to clients. For this, I want to do it as follows: Client creates a socket connection and subscribes destination: var socket = new SockJS('/websocket'); var stompClient = Stomp.over(socket); stompClient.connect({}, function (frame) { stompClient.subscribe('/product/changes', function (scoredata) { // We received product changes }); }); //Send Ajax request and say server I want to know product with id=5 changes. sendAjaxRequest(5); I

问题 TL;DR; We are trying to design a WebSocket server using spring webflux WebSocket implementation. The server has usual HTTP server operations e.g. create/fetch/update/fetchall . Using WebSockets we were trying to expose one endpoint so the clients could leverage a single connection for all sort of operations, given WebSockets are meant for this purpose. Is it a right design with webflux and WebSockets? Long Version We are starting a project which is going to use reactive web sockets from