4 ms·
I have it disabled all the time. It doesn't help. The redirect is done by the server, before it had a chance to learn if the client supports JS or not: $ wg
by jwilk 8y ago
I have it disabled all the time. It doesn't help.
The redirect is done by the server, before it had a chance to learn if the client supports JS or not:
$ wget --max-redirect=0 https://www.forbes.com/sites/gordonkelly/2018/09/08/microsoft-windows-7-monthly-charge-windows-10-free-upgrade-cost/
--2018-09-09 19:07:58-- https://www.forbes.com/sites/gordonkelly/2018/09/08/microsoft-windows-7-monthly-charge-windows-10-free-upgrade-cost/
Resolving www.forbes.com (www.forbes.com)... 151.101.114.49
Connecting to www.forbes.com (www.forbes.com)|151.101.114.49|:443... connected.
HTTP request sent, awaiting response... 302 Found
Location: https://www.forbes.com/consent/?toURL=https://www.forbes.com/sites/gordonkelly/2018/09/08/microsoft-windows-7-monthly-charge-windows-10-free-upgrade-cost/ [following]
0 redirections exceeded.
- dvfjsdhgfv 8y agoThat's very interesting. For me the behavior is 100% consistent. Paste the URL in the address bar with JS enabled - get a blank page. Paste it with JS disabled - get straight to the destination.