4 ms·
No, in fact now t.co even returns an empty body with it's 301 response: % curl -vgsSw'< HTTP/size %{size_download}\n' https://t.co/DzIiCFp7Ti 2>&1 | grep '^<
by mzs 3y ago
No, in fact now t.co even returns an empty body with it's 301 response:
% curl -vgsSw'< HTTP/size %{size_download}\n' https://t.co/DzIiCFp7Ti 2>&1 | grep '^< \(HTTP/\)\|\(location: \)'
< HTTP/2 301
< location: https://www.threads.net/@chaco_mmm_room
< HTTP/size 0
- flutas 3y agoFirefox: <head><noscript><META http-equiv="refresh" content="0;URL=https://www.threads.net/@chaco_mmm_room"></noscript><title>https://www.threads.net/@chaco_mmm_room</title></head><script>window.opener = null; location.replace("https:\/\/www.threads.net\/@chaco_mmm_room")</script>
- mzs 3y agoTurns-out it depends on the User-Agent: https://news.ycombinator.com/item?id=37139425 https://news.ycombinator.com/item?id=37139425
- mlyle 3y agoYou didn't read the second paragraph of the comment you replied to-- which explained this exact issue before you replied "no": > You don't see this with curl/wget because they use user agent sniffing. If they don't think you're a browser they _will_ give you a Location header. To see it, capture a request in Firefox developer tools, right click on the request, copy as CURL.
- mzs 3y agoIndeed, sorry everyone