[wp-trac] [WordPress Trac] #34563: URL structure for providing oEmbed should be made easier to block at webserver

WordPress Trac noreply at wordpress.org
Tue Nov 3 07:58:58 UTC 2015


#34563: URL structure for providing oEmbed should be made easier to block at
webserver
--------------------------+-----------------------------
 Reporter:  mark-k        |      Owner:
     Type:  defect (bug)  |     Status:  new
 Priority:  normal        |  Milestone:  Awaiting Review
Component:  Embeds        |    Version:  trunk
 Severity:  normal        |   Keywords:
  Focuses:                |
--------------------------+-----------------------------
 This follows a very troolish discussion at the tavern
 http://wptavern.com/wordpress-4-4-streamlines-content-sharing, with the
 usual theme of not enough options in core, But there is one take away,
 that blocking features in PHP level is not ideal.

 Right now if I don't want that my site will be an oEmbed provider, I still
 need to "pay" the price of loading core, plugins and parsing the URL.
 Worse scenarion is if I already was (wordpress default) and decided to
 turn it off, then I will still be hammered by requests from sites that
 still think I do provide oEmbed.

 A site owner might want to fully disable the feature, or limit it to
 syndication partners, and the best way performance wise is to set the
 relevant rules in htaccess or any applicable web server config file. The
 current url structure seems to be too difficult for that (I assume you can
 block URLs that have oembed=1 but it is probably more error prone then
 blocking something like oembed.php)

--
Ticket URL: <https://core.trac.wordpress.org/ticket/34563>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform


More information about the wp-trac mailing list