Comment

Comment by nantes

It appears to just be an HTTP 301 redirect, so you could use something like curl to unroll it:

  curl -I https://www.tiktok.com/t/ZTRmqkW4N
produces:

  HTTP/2 301 
  server: nginx
  content-type: text/html; charset=utf-8
  location: https://www.tiktok.com/@spencer.sebastian.yang/video/7149578560230034734?_t=8W9Y6CPjvbf&_r=1
Trim off the GET params (the bit after the ? in the URL) and you get <https://www.tiktok.com/@spencer.sebastian.yang/video/7149578...>. That appears to load in a browser for me.

I did check to see if that resulting URL after the first redirect is also a redirect. It is not, but also returned an HTTP 403 response ('Forbidden'), when submitted without cookies that had been added.

parent nantes 4 years ago

Discussion

Live from the official Hacker News API

A modern reader for Hacker News · SvelteKit + Skeleton