Forum
Notifications
Clear all
Topic starter
05/06/2025 10:51 pm
I am running into a stubborn WebSocket issue with SignalR behind a Skudonet 7.2.1 appliance.
The browser console keeps showing like screenshot
Headers
X-Frame-Options: SAMEORIGIN
X-Content-Type-Options: nosniff
Referrer-Policy: strict-origin-when-cross-origin
Content-Security-Policy-Report-Only: default-src 'self' https:; script-src 'self' 'unsafe-inline' https:; style-src 'self' 'unsafe-inline' 'unsafe-hashes'; img-src 'self' data: https:; connect-src 'self' https: wss:; object-src 'none'; base-uri 'self'; frame-ancestors 'none'
Permissions-Policy: accelerometer=(), camera=(), geolocation=(), gyroscope=(), magnetometer=(), microphone=(), payment=(), usb=(), interest-cohort=(), browsing-topics=()
X-XSS-Protection: 1; mode=block
X-Permitted-Cross-Domain-Policies: none
Expect-CT: max-age=0, enforce
# Persistence
Mode .................... IP: Client address
Session TTL ............. 1800 s
# Advanced
Rewrite location headers Enabled
HTTP verbs accepted ..... + MS RPC extensions verbs
100-Continue mode ....... Ignore
Backend connection timeout 300 s
Backend response timeout 300 s
Client request timeout 300 s
Frequency to check resurrected back-ends 21 s
Are there additional CLI flags that must be enabled for WebSockets in version 7.2.1?
Anything else that can make Skudonet drop the Upgrade: websocket request silently?
