Welcome • User Guide
ToS • Privacy • Canary
Donate • Bugs • License

©2025 Poal.co

1.3K

Now, using web.archive.org/save/[url] instantly redirects to the saved page.

It now uses the same user agent it would use when using their new submission form (web.archive.org).

Try it out: https://web.archive.org/save/twitter.com/jack/status/20 .

Now, using `web.archive.org/save/[url]` instantly redirects to the saved page. It now uses the same user agent it would use when using [their new submission form](https://web.archive.org/save/). Try it out: https://web.archive.org/save/twitter.com/jack/status/20 .

(post is archived)

[–] • 0 pt

Update: They just brought the legacy liveweb option back.

(I.e. everything is like before March 10th: The Live Web proxy preview is back and passes through the user agent.)

But for files (e.g. PDF), it has always been without the Liveweb. Nothing has changed there.

[–] • 0 pt

Because some websites (e.g. Twitter) might alter their loaded content based on the browser's user agent, it would be good if the Wayback Machine manually optionally allowed setting the user agent and also seeing which user agent was used to archive which page.

[–] • 0 pt

Now

  • Lets browser wait for response while archiving page in background using new method.
  • Redirects to saved page using HTTP 302 response.

Earlier (liveweb method)

  • Loads preview of saved page
  • Redirects to saved target page using JavaScript function.