Description of the issue:
My problem relates specifically to the Brave web-browser and it’s native ‘Brave Shield’ blocking my back-end web-socket which I suspect is due to ‘fingerprinting’. This may be a web-dev related question.
On all other browsers, my website will load, and a connection to my back-end websocket is made with no issues. However, with the Brave Browser and the Brave Shield turned on - the client refuses to connect to my websocket.
Perhaps someone else has run into the same problem and found a resolution aside from asking users to disable the Brave Shield?
Exact URL of the website in question:
**Did the issue present with [default Shields settings]
Does the site function as expected when Shields are turned off?
Is there a specific Shields configuration that causes the site to break? If so, tell us that configuration. (yes/no):
When blocking fingerprinting, the site does not connect to websocket.
Does the site work as expected when using Chrome?
Brave version (check