Websocket behind Access
If your question is how you can use Websockets behind Access: They work just as normal http requests do, if you authenticate with Access you can use Websockets
If your question is: How can I poke a hole in my access config to let anyone use websockets but leave the rest protected? You can't filter for just websocket/upgrade requests, but you can create an application with a more specific path: https://developers.cloudflare.com/cloudflare-one/policies/access/app-paths/ and a Bypass/Service Auth Policy allowing everyone. That would only work if the websocket uses one or a few specific paths like
If your question is: How can I poke a hole in my access config to let anyone use websockets but leave the rest protected? You can't filter for just websocket/upgrade requests, but you can create an application with a more specific path: https://developers.cloudflare.com/cloudflare-one/policies/access/app-paths/ and a Bypass/Service Auth Policy allowing everyone. That would only work if the websocket uses one or a few specific paths like
/wss which you would create a new self-hosted application in Access to coverApplication paths define the URLs protected by an Access policy. When adding a self-hosted web application to Access, you can choose to protect the …
