4 ms·
This can often be solved by prepending https://web.archive.org/web/*/ to the now broken URL.
by pygy_ 11y ago
This can often be solved by prepending
https://web.archive.org/web/*/
to the now broken URL.
- kbenson 11y agoHmm, there must be some extension that detects 404 errors and/or server unresponsive and prompts whether you want to check Google's cache or the Internet archive. That browsers haven't already integrated this (with a configurable list of archiving services, like search engines), is actually rather surprising to me.
- pygy_ 11y agoThere are extensions with that kind of functionality, but by now I have that sequence hardwired in my fingers.
- slrz 11y agoThere is: Resurrect Pages. https://addons.mozilla.org/en-US/firefox/addon/resurrect-pages/ https://addons.mozilla.org/en-US/firefox/addon/resurrect-pag... https://github.com/arantius/resurrect-pages https://github.com/arantius/resurrect-pages
- greglindahl 11y agoThere are many such extensions, but yes, we're working on getting directly integrated into Firefox, Chrome, Edge, and if anyone has a contact at Safari (or one of the other browsers), my email addr is in my profile. Thanks.
- gpvos 11y agoAnd then finding that the page is blocked by a robots.txt that is present now, but probably wasn't when the page originally existed.
- pygy_ 11y agoRobots.txt is respected retroactively?
- gpvos 11y agoYes, but it is only temporary. As long as you have a robots.txt file excluding some URLs, those URLs will: 1) not be crawled by the Internet Archive crawler, 2) not be shown in the Wayback Machine. Any already-crawled pages will, however, invisibly remain in the archive, and will reappear once they are not in the robots.txt anymore.