internetarchive / internetarchive/dweb-archive

YouTube: Opening earlier capture redirects to parameterized URL

Open
#174 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
JavaScript
Stars
59
Forks
15
PR merge metrics
No merged PRs in 30d

Description

**Issue**: When viewing an archived YouTube URL, opening an earlier capture will sometimes redirect to a separate parametrized version of the URL. This version may display a different number of captures than the original page.

**Steps to reproduce:**

1. Open capture for [SteamWorld Dig trailer for 2014-01-03](https://web.archive.org/web/20140103200158/http://www.youtube.com/watch?v=T_TozS-qSYI).
2. Note the number of captures. (6 at time of writing)
3. Click the back arrow to open the earlier archive from 2013-09-15.

**Expected result:**

The archive URL is not changed. 6 captures are listed. (See https://web.archive.org/web/20180930071136/https://www.youtube.com/watch?v=T_TozS-qSYI)

**Actual result:**

The archive URL changes to a parameterized version ending in `&gl=US&hl=en`. Only 1 capture is listed. (See https://web.archive.org/web/20130915122818/http://www.youtube.com/watch?v=T_TozS-qSYI&gl=US&hl=en)

**Screenshots**:

2014 archive without URL parameters, lists 6 captures.
![image](https://user-images.githubusercontent.com/1330770/69988011-c2ca8880-150e-11ea-9ef2-d4861916e2f4.png)

2013 archive with URL parameter, lists 1 capture.
![image](https://user-images.githubusercontent.com/1330770/69988053-da097600-150e-11ea-81a0-3b99dcfc074b.png)

2013 archive without URL parameters (manually removed), lists 6 captures.
![image](https://user-images.githubusercontent.com/1330770/69988088-ea215580-150e-11ea-9b64-2a584cfe99e2.png)

Contributor guide

No contributing guide indexed for this repository

Research direction

Reproduce the two linked archive URLs and use the back arrow from the 2014-01-03 YouTube capture to the 2013-09-15 capture. Trace the archive navigation and URL handling from that entry point; done means the URL stays unparameterized and the earlier capture lists all 6 captures, as shown in the expected and manually corrected examples.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
frontend
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
48/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.