2 ms·
The technical method of the blocking is indeed interesting. From my home broadband connection: - I can connect to port 80 on fallback.global-ssl.fastly.net (t
by rahimnathwani 13y ago
The technical method of the blocking is indeed interesting. From my home broadband connection:
- I can connect to port 80 on fallback.global-ssl.fastly.net (to which the CNAME entry for www.theguardian.com points).
- I can successfully get a 404 page (from that same server) by doing something like this: GET / HTTP/1.1 Host:www.invaliddomain.com
- I get disconnected if I specify Host: www.theguardian.com in any HTTP request, even if I'm connecting to some IP address that has no relationship with theguardian.com.
So, in this instance, the GFW is not blocking by IP address, nor is it blocking by keyword. It is blocking by the hostname in the Host: header of the HTTP request.
- jychang 13y agoThis implies that HTTPS would easily bypass it. If only the Guardian had HTTPS support...
- rahimnathwani 13y agoSadly it's not as simple as that. Facebook has HTTPS support, but TCP connections on port 443 just time out. The GFW is sophisticated. It would be trivial to stop all obvious VPN traffic (obvious = PPTP and L2TP/ipsec on default ports) without affecting other things, but this isn't done, unless many people connect to the same server over some period of time. Unidentifiable TCP/UDP traffic on other ports (e.g. OpenVPN on a port number in the 1000s) again isn't blocked. However, if the same TCP/UDP port on the same server is accessed for long enough, and often enough, it will get blocked. Switching to a different port on the same server will probably fix it, until the next time.