this post was submitted on 02 Dec 2023
2 points (100.0% liked)

Piracy: ꜱᴀɪʟ ᴛʜᴇ ʜɪɢʜ ꜱᴇᴀꜱ

55016 readers
576 users here now

⚓ Dedicated to the discussion of digital piracy, including ethical problems and legal advancements.

Rules • Full Version

1. Posts must be related to the discussion of digital piracy

2. Don't request invites, trade, sell, or self-promote

3. Don't request or link to specific pirated titles, including DMs

4. Don't submit low-quality posts, be entitled, or harass others



Loot, Pillage, & Plunder

📜 c/Piracy Wiki (Community Edition):


💰 Please help cover server costs.

Ko-Fi Liberapay
Ko-fi Liberapay

founded 2 years ago
MODERATORS
 

For example, this invidious instance offers a download option for a YoutTube video, as that instance does for all YT videos:

~~https://invidious.fdn.fr/watch?v=lU4vv7qCQvg~~ (see update)

Exceptionally, if you opt to download it it merely opens a player to watch realtime. While other downloads from the same invidious instance have no issues. Why is this one getting different treatment?

update Apparently it’s an instance-specific problem with that particular video:

works → https://invidious.fdn.fr/watch?v=lU4vv7qCQvg

broken → https://iv.ggtyler.dev/watch?v=lU4vv7qCQvg

I’ve seen other instances where this particular video download is broken. AFAIK, invidious.fdn.fr is the only place where it works as expected.

you are viewing a single comment's thread
view the rest of the comments
[–] Nomad@infosec.pub 4 points 1 year ago (2 children)

This is your browser handling the content disposition wrongly.

[–] ciferecaNinjo@fedia.io 0 points 1 year ago (1 children)

Why would a browser handle it incorrectly for one video on one invidious instance, but not for most other videos and other instances?

Note that I’ve seen this broken behavior both in my own Chromium installation as well as Firefox in Windows as a public library.

[–] shnizmuffin@lemmy.inbutts.lol 1 points 1 year ago

There are a few reasons this might be the case!

  1. The instance's UI might not be declaring that a or button element as a resource meant to be downloaded.

  2. The instance's web server might not have declared the downloadable file's mime type as a resource. (Apache, nginx.)

  3. Your operating system might not recognize the file type as a thing to be downloaded, or your browser isn't telling it to download to a file.

It's probably 1 or 2 if you're seeing the same behavior across multiple browsers and OS.