[wp-trac] [WordPress Trac] #26844: Twitter oembeds not working because of Twitter API change

[WordPress Trac]

#26844: Twitter oembeds not working because of Twitter API change
--------------------------+--------------------
 Reporter:  yurivictor    |       Owner:
     Type:  defect (bug)  |      Status:  new
 Priority:  normal        |   Milestone:  3.9
Component:  Embeds        |     Version:  trunk
 Severity:  normal        |  Resolution:
 Keywords:  needs-patch   |
--------------------------+--------------------

Comment (by nacin):

 Things to investigate:
  * If we make this change, we abandon sites that don't support OpenSSL.
 That's OK, since obviously Twitter forced our hand on that. I've reached
 out to the developer advocate who announced this
 (https://twitter.com/nacin/status/423548186167226368).
  * Do we (and if not, why not) follow the redirect here? Is the issue
 OpenSSL, WordPress, or Twitter? (See possibility below...)

 So — while
 http://api.twitter.com/1/statuses/oembed.json?id=423546680999301121
 redirects in a browser, yurivictor pointed out that `curl --head` gets a
 403. Why? Would be good to investigate and report that back to Twitter. If
 they can fix that, then all existing WordPress installs (that support
 OpenSSL) should follow this redirect without an issue.

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