Getyarn link causes .mp4 download

AI-generated summary

Users reported that embedding links from getyarn.io causes browsers to download .mp4 files instead of playing them inline, likely due to the site serving content with the MIME type application/mp4 instead of video/mp4. LockeCJ noted the issue also triggers on post re-rendering. Simsnet and pfaffman speculated it’s a server-side MIME type misconfiguration, possibly on getyarn.io’s end. codinghorror asked if Discourse could intervene, prompting eviltrout to test on try.discourse.org — where it worked fine, suggesting getyarn.io may have since fixed the issue. LockeCJ agreed the problem appeared resolved. Further testing by codinghorror revealed inconsistent behavior: autoplay worked once in Firefox but not Chrome, hinting at possible browser-specific rendering quirks. The consensus leans toward the issue being external to Discourse, likely resolved by getyarn.io’s server changes.

Similar to

Posting a link to a getyarn.io clip appears to onbox in the preview, but the actual post causes the browser to download a .mp4 file. More annoyingly, this happens any time the post comes into view, since I assume it’s being re-rendered.

It looks like the content type served by getyarn.io is application/mp4 instead of video/mp4, so that may be relevant.

Here’s an example URL, escaped for obvious reasons:

https://getyarn.io/yarn-clip/d371f408-aea1-4508-9d56-c60898827e44

This bugs me too…I’ve always to know how to change a site’s MIME type…happens a lot with my web server (it’s something, no clue if Apache, nginx, JBossWeb, etc)

Sounds like a problem with getyarn.io. Have you asked them why they use what you describe as the wrong mime type?

Anything we can do here @eviltrout?

1 лайк

I just tried it on https://try.discourse.org and it worked fine? Is it possible they fixed the MIME type or is this a browser specific issue? I tested on the latest Chrome.

4 лайка

Here’s the embed from above, let’s see if it works?

https://getyarn.io/yarn-clip/d371f408-aea1-4508-9d56-c60898827e44

Agreed that they must have changed something on their end.

Thanks for looking into it!

2 лайка

This topic was automatically closed after 4 days. New replies are no longer allowed.

Let’s see

This seems to autoplay (once) on Firefox but not in Chrome for me.