Skip to main content

View Post [edit]

Poster: EarthFurst Date: Jan 3, 2015 5:15pm
Forum: web Subject: Re: Wayback Machine not archiving anything

Wayback ok for the most part, but Wayback a few minutes ago was having difficulty archiving a waypage Initial attempts to archive http://gurukittystudios.deviantart.com/journal/Vcon-Report-261534788 resulted in usual "Saving page now" message, BUT was getting sent back to "Hrm. Wayback Machine doesn't have that page archived. This page is available on the web! Help make the Wayback Machine more complete! Save this url in the Wayback Machine" EDIT: bring this up as this problem of-getting-sent-back-to-HRM page keep re-occuring.
This post was modified by EarthFurst on 2015-01-04 01:15:40

Reply [edit]

Poster: TL7 Date: Jun 14, 2017 2:09pm
Forum: web Subject: Happening on some different websites too. Possible JavaScript infinite loop.

Hello.
Instagram and some subdomains of YouTube are suffering from this problem.
Additionally, some websites have messed HTTP headers/response codes and messy JavaScript, which could be the cause.

Reply [edit]

Poster: PiRSquared Date: Jan 5, 2015 12:23pm
Forum: web Subject: Re: Wayback Machine not archiving anything

It seems to intermittently break. Can staff please look into this?

For example, trying to save the following URLs does not work:

https://web.archive.org/save/http://insights.wired.com/profiles/blogs/end-to-big-data?utm_source=eicker&utm_medium=twitter
(but the version without the query string works)

Reply [edit]

Poster: EarthFurst Date: Feb 5, 2015 3:22am
Forum: web Subject: Re: Wayback Machine not archiving anything

Possibly related (both errors involve the & symbol) Example: At https://web.archive.org/web/*/http://irc.netsplit.de/channels/details.php?room=%23gamerfurs&net=FurNet Wayback says it has three waybacks of http://irc.netsplit.de/channels/details.php?room=%23gamerfurs&net=FurNet which says "Saved 3 times between July 1, 2007 and July 5, 2011." BUT when I click on THAT "July 1, 2007" or THAT "July 5, 2011." I end up at another webpage that says "... Hrm. Wayback Machine doesn't have that page archived. Want to search for all archived pages under http://irc.netsplit.de/channels/ ?" *** Similar problem with https://web.archive.org/web/*/https://www.second-ed.com/results.cfm?Category=04&subcat=ALL says "Saved 8 times between July 8, 2008 and October 22, 2013.", but if I click on THAT "July 8, 2008" or THAT "October 22, 2013" also end up at "Hrm. Wayback Machine doesn't have that page archived. ..." EDIT: and if I try to archive latest version of https://www.second-ed.com/results.cfm?Category=04&subcat=ALL I end with "Bummer. This url is not available on the live web or can not be archived. ... "
This post was modified by EarthFurst on 2015-02-05 11:22:43

Reply [edit]

Poster: PiRSquared Date: Feb 5, 2015 5:20pm
Forum: web Subject: Jeff, please forward this to Wayback Machine people

It's because the link is being escaped twice. (NOTE: The display text of the links below are wrong because the forum software is broken too.) The broken link is: https://web.archive.org/web/20110705220201/http://irc.netsplit.de/channels/details.php?room=%23gamerfurs&net=FurNet The working one is: https://web.archive.org/web/20110705220201/http://irc.netsplit.de/channels/details.php?room=%23gamerfurs&net=FurNet Basically, the ampersand (&) part is wrong.
This post was modified by PiRSquared17 on 2015-02-06 01:20:04

Reply [edit]

Poster: EarthFurst Date: Feb 5, 2015 10:31pm
Forum: web Subject: Re: Jeff, please forward this to Wayback Machine people

I noticed the forum broke the URLs (truncated URLs after the ampersand),

but I had NOT noticed the forum had inserted a semi-colon after the ampersand.

PiRSquared17 : how did you get URL to post correctly in the forum without truncation and without the forum inserting a semi-colon after the ampersand?

Reply [edit]

Poster: PiRSquared Date: Feb 6, 2015 7:47pm
Forum: web Subject: Re: Jeff, please forward this to Wayback Machine people

I had to use & to get &... very confusing to figure out how to escape these correctly, especially when you're trying to discuss URL escaping itself! It seems we've found escaping problems in both the forums and the Wayback Machine.