Do you think this problem and linked Vaadin bug fix would apply to the sporadic “invalid JSON” errors mentioned in communication-error-invalid-json-from-server-1-x and jmix-1-x-app-not-working-on-aws-communication-error-invalid-json-from-server-1-x ??
I have been having the invalid JSON error and found these NGINX log entries that correspond. They all had 403 response to POST /VAADIN/push, so this is why I thought they may be related. In my case there was a GET /VAADIN/push that received 101 and is immediately followed by the POST that receives 403.
My app is running on AWS Beanstalk w/ standard NGINX configuration.
Here are the sanitized entries from the NGINX log. There was nothing in the application log.
[09/Apr/2024:22:59:40 +0000] "GET /VAADIN/push?v-r=push&v-uiId=0&v-pushId=1b557a50-233f-4b89-8634-6fe69ba7be98&X-Atmosphere-tracking-id=0&X-Atmosphere-Framework=3.1.2-javascript&X-Atmosphere-Transport=websocket&X-Atmosphere-TrackMessageSize=true&Content-Type=application/json;%20charset=UTF-8&X-atmo-protocol=true&X-Vaadin-LastSeenServerSyncId=0 HTTP/1.1" 101 51 "-" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/123.0.0.0 Safari/537.36" "my IP address"
[09/Apr/2024:22:59:40 +0000] "POST /VAADIN/push?v-r=push&v-uiId=0&v-pushId=1b557a50-233f-4b89-8634-6fe69ba7be98&X-Atmosphere-Transport=close&X-Atmosphere-tracking-id=9e157618-38d9-4cef-99f0-26ecd1ecdf3d&X-Vaadin-LastSeenServerSyncId=3 HTTP/1.1" 403 111 "https://server/login" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/123.0.0.0 Safari/537.36" "my IP address"