[wp-trac] [WordPress Trac] #45033: Add TIDAL to oEmbed whitelist

[WordPress Trac]

#45033: Add TIDAL to oEmbed whitelist
-------------------------+----------------------
 Reporter:  tidal        |       Owner:  (none)
     Type:  enhancement  |      Status:  closed
 Priority:  normal       |   Milestone:
Component:  Embeds       |     Version:
 Severity:  normal       |  Resolution:  wontfix
 Keywords:  needs-patch  |     Focuses:
-------------------------+----------------------

Comment (by tidal):

 Hi again!

 Thanks for all the feedback!

 The oEmbed discovery link on our Browse-pages are constructed like so:


 {{{
 <link rel="alternate" type="application/json+oembed"
 href="http://oembed.tidal.com/?url=https://tidal.com/track/94560983" />
 }}}

 The URL parameter is set to https://tidal.com/track/94560983, not the
 browse page URL. (https://tidal.com/browse/track/94560983 )

 Why would WordPress attempt to call the endpoint with another URL than
 what's specified by the discovery tag, like @swissspidy observed? We can
 easily add support for Browse page URLs in our oEmbed API if needed, but I
 do not get how WordPress could ever call them?

 @peterwilsoncc, the iframe in the html property of the response from the
 oEmbed API will always be https. Did you mean that the oEmbed discovery
 link is not? I'll look into why it's not specified as https there, it
 should be!

 Kind regards,\\
 Jeremy Karlsson\\
 TIDAL

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/45033#comment:4>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform