zlacker

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

replies(2): >>flutas+S >>mlyle+6N

>>mzs+(OP)
Firefox:

    <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>

replies(1): >>mzs+d4

>>flutas+S
Turns-out it depends on the User-Agent: >>37139425

>>mzs+(OP)
You 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.

replies(1): >>mzs+D22

>>mlyle+6N
Indeed, sorry everyone