Well it looks like you're perfectly capable of handling a full response :) Here's what's going on exactly:
In our great age of surveillance, there are cases where companies, even ISPs have web proxies in place. The problem here is that my website makes heavy use of websockets on port 7340. Most proxies haven't caught up to websockets yet because it's still a fairly new tech.
So my website sees you connect from one IP (the proxy) on port 443 and another IP (unproxied external IP) on port 7340. And it's not too happy about that because it thinks someone is trying to get to the websocket without going through the front door and establishing a session.
Of course there's also cases where people have proxies because they have malware installed... There's is a very fine line between malware and surveillance wouldn't you know it? :)
I do have the usual stats gathering JS on there which is what's triggering uBlock and cookies, but they are 100% non-essential to the good running of the site. The websocket on the other hand isn't unfortunately.
I'm not sure what I should do if anything, I've had a few folks report this so maybe I need to do something. Or maybe I can be ok with the fact that corporate networks with non-standard rules will break things. Tough call...
Anyway, thank you for giving me more details to think about this. And sorry it doesn't just work for you. It should definitely work from home :).
Thank you for the quick and thorough response! I will definitely try this from home. I love web tools (I wrote a really terrible wireframe tool when I discovered Ajax back in 2006 and it's still alive, and still terrible, but last I checked a lot of people played with it!) and from what I've seen of samples and screenshots, it's very neat and visually interesting.
In our great age of surveillance, there are cases where companies, even ISPs have web proxies in place. The problem here is that my website makes heavy use of websockets on port 7340. Most proxies haven't caught up to websockets yet because it's still a fairly new tech.
So my website sees you connect from one IP (the proxy) on port 443 and another IP (unproxied external IP) on port 7340. And it's not too happy about that because it thinks someone is trying to get to the websocket without going through the front door and establishing a session.
Of course there's also cases where people have proxies because they have malware installed... There's is a very fine line between malware and surveillance wouldn't you know it? :)
I do have the usual stats gathering JS on there which is what's triggering uBlock and cookies, but they are 100% non-essential to the good running of the site. The websocket on the other hand isn't unfortunately.
I'm not sure what I should do if anything, I've had a few folks report this so maybe I need to do something. Or maybe I can be ok with the fact that corporate networks with non-standard rules will break things. Tough call...
Anyway, thank you for giving me more details to think about this. And sorry it doesn't just work for you. It should definitely work from home :).