Closed pronebird closed 6 years ago
Is this a bug on our side? Could we be doing this right according to the spec? Or should this rather be fixed at Wordpress?
@astro hi, I hardly can comment on this as it's been a year since I reported this issue. It might be that this issue does not exist anymore...
Closing due to absence of interest in proceeding with this PR.
WordPress has some issues with "for" parameter encoded in final URL fo some reason. So the request looks like this: http://public-api.wordpress.com/oembed/1.0/?format=json&url=http%3A%2F%2Frodp.wordpress.com%2F2013%2F02%2F27%2Fon-scorpions-and-frogs%2F&for=wpcom-auto-discovery But the last "for" parameter should be a part of API URL, not as part of blog post URL, otherwise WP returns 501. Embed.ly handles this flawlessly at least..