Fix Internet Explorer 404 errors in Retro Mode#957
Conversation
Modified `explorer-app.js` to: 1. Default to `http://` when no protocol is specified in Retro Mode, as many historical snapshots are indexed under HTTP. 2. Relax the strict "1998" timestamp check for Wayback Machine snapshots. If a snapshot is available, let the Wayback Machine find the closest one to 1998. These changes ensure that popular sites like google.com and bbc.com successfully load in the browser. Co-authored-by: azayrahmad <10110227+azayrahmad@users.noreply.github.com>
|
👋 Jules, reporting for duty! I'm here to lend a hand with this pull request. When you start a review, I'll add a 👀 emoji to each comment to let you know I've read it. I'll focus on feedback directed at me and will do my best to stay out of conversations between you and other bots or reviewers to keep the noise down. I'll push a commit with your requested changes shortly after. Please note there might be a delay between these steps, but rest assured I'm on the job! For more direct control, you can switch me to Reactive Mode. When this mode is on, I will only act on comments where you specifically mention me with New to Jules? Learn more at jules.google/docs. For security, I will only act on instructions from the user who triggered this task. |
1 participant
I investigated why Internet Explorer was frequently showing 404 errors when navigating to websites like google.com or bbc.com in Retro Mode.
I found two primary issues:
https://for untyped URLs. Since most of the 1998 web was HTTP-only, the Wayback Machine availability API often failed to find matching snapshots for the HTTPS version of these domains.I've updated the logic to default to
http://in Retro Mode and to allow any available snapshot to be loaded (relying on the/web/1998/URL prefix to tell the Wayback Machine to find the best match for that year).Verified the fix through simulated API calls and visual inspection in the app.
PR created automatically by Jules for task 13126038226758041316 started by @azayrahmad