11–20 of 78 posts
CF WS support means I will no longer have to keep around a separate, direct-to-server (sub)domain around for my WebSockets projects, and this also means goodbye to any websockets-related SSL certificate hassle in this regard.
Curious why they hadn't been doing this all along. This seems like low hanging fruit to add value. Maybe I'm missing something.
Except if you are behind a restrictive corporate firewall that filters anything not in RFC 2616.
Usually not much of a problem behind HTTPS (or wss:// in this case).
Except if you are behind a restrictive corporate firewall that filters anything not in RFC 2616.
If you are using secure web sockets (wss), this shouldn't be an issue as the traffic goes over port 443 and the proxy won't be able to tell if it's HTTP or another type of traffic.
Except if you are behind a restrictive corporate firewall that filters anything not in RFC 2616.
If you are using secure web sockets (wss), this shouldn't be an issue as the traffic goes over port 443 and the proxy won't be able to tell if it's HTTP or another type of traffic.
Curious why they hadn't been doing this all along. This seems like low hanging fruit to add value. Maybe I'm missing something.
Earlier quoted context omitted.
If you are using secure web sockets (wss), this shouldn't be an issue as the traffic goes over port 443 and the proxy won't be able to tell if it's HTTP or another type of traffic.
Don't many companies install their own certificate on company-owned machines so they can MITM secure traffic too?
However, I've often seen port 443 being blocked :|.
Earlier quoted context omitted.
Usually not much of a problem behind HTTPS (or wss:// in this case).
https://www.howtoforge.com/filtering-https-traffic-with-squi...
Earlier quoted context omitted.
Don't many companies install their own certificate on company-owned machines so they can MITM secure traffic too?
I've never seen that. Also, this would break many websites that are part of the HPKP preload list I would think (need to double check), which include most popular websites. However, I've often seen port 443 being blocked :|.