#11556 closed enhancement (fixed)
Add support for embedding YouTu.be URLs
Reported by: | Viper007Bond | Owned by: | |
---|---|---|---|
Milestone: | 3.0 | Priority: | normal |
Severity: | normal | Version: | 2.9 |
Component: | Embeds | Keywords: | has-patch tested |
Focuses: | Cc: |
Description
http://youtube-global.blogspot.com/2009/12/make-way-for-youtube-links.html
Allows you to embed them. Needs to be transformed internally as their oEmbed provider doesn't support them. Adds a new filter to do it.
Attachments (2)
Change History (13)
#4
in reply to:
↑ 3
@
14 years ago
Replying to westi:
Could we not just register youtu.be as another oembed provided and rely on the 302 following of the HTTP handlers.
That way we don't need any youtu.be specific code in here and if they change the url format of any of the providers in future and offer 302 redirects we would follow those too?
No, because their oEmbed provider doesn't understand their shortened URLs.
Example short URL: http://youtu.be/nTDNLUzjkpg
Their provider returns a 401 for that URL: http://www.youtube.com/oembed?format=xml&url=http%3A%2F%2Fyoutu.be%2FnTDNLUzjkpg
Ideally their oEmbed provider should support their short URLs. I didn't think that'd be possible, however I recently saw one of the YouTube people post to the oEmbed mailing list, so I'll see if I can get them to support their short URLs so we can just map them directly to their oEmbed provider.
#6
@
14 years ago
- Milestone 3.0 deleted
- Resolution set to worksforme
- Status changed from new to closed
YouTube's oEmbed provider now understands shortened URLs.
#8
follow-up:
↓ 9
@
14 years ago
- Resolution worksforme deleted
- Status changed from closed to reopened
Actually, we still need to add that format to the whitelist, we just don't need a remapping function.
#9
in reply to:
↑ 8
@
14 years ago
Replying to Viper007Bond:
Actually, we still need to add that format to the whitelist, we just don't need a remapping function.
Oops, yep.
Could we not just register youtu.be as another oembed provided and rely on the 302 following of the HTTP handlers.
That way we don't need any youtu.be specific code in here and if they change the url format of any of the providers in future and offer 302 redirects we would follow those too?