Imgur API requires SSL

[GunGeekATX]

The Imgur API URL currently in core is ​http://api.imgur.com/oembed but it now requires SSL.

​http://api.imgur.com/oembed?maxwidth=525&maxheight=788&url=https%3A%2F%2Fimgur.com%2FTJ8UIuP&format=json

{
    "data": {
        "error": "HTTP Access is disabled. Requests must use SSL (HTTPS)."
    },
    "success": false,
    "status": 400
}

[danieltj]

This seems to be working by design, no? The URL you've included returns the following JSON response for me:

{"version":"1.0","type":"rich","provider_name":"Imgur","provider_url":"https:\/\/imgur.com","width":525,"height":788,"html":"<blockquote class=\"imgur-embed-pub\" lang=\"en\" data-id=\"TJ8UIuP\"><a href=\"https:\/\/imgur.com\/TJ8UIuP\">View post on imgur.com<\/a><\/blockquote><script async src=\"\/\/s.imgur.com\/min\/embed.js\" charset=\"utf-8\"><\/script>"}

Did you try adding an image in the WYSIWYG editor or the above link?

[GunGeekATX]

Give it a try with curl or wget. In Chrome, I noticed it automatically redirecting.

vagrant@vvv:/srv/www/wordpress-default$ wget http://api.imgur.com/oembed?maxwidth=525&maxheight=788&url=https%3A%2F%2Fimgur.com%2FTJ8UIuP&format=json
[1] 26635
[2] 26636
[3] 26637
vagrant@vvv:/srv/www/wordpress-default$ --2017-09-25 14:41:34--  http://api.imgur.com/oembed?maxwidth=525
Resolving api.imgur.com (api.imgur.com)... 151.101.48.193
Connecting to api.imgur.com (api.imgur.com)|151.101.48.193|:80... connected.
HTTP request sent, awaiting response... 400 Unknown Error
2017-09-25 14:41:34 ERROR 400: Unknown Error.

[dd32]

Changing the API url to https:// seems good, and required. The HTTP api is definitely unresponsive.

A note for testing, api.imgur.com seems to have a 403 Permission Denied response for any user-agents containing 'wordpress' (specifically in lower-case) anywhere in it's string. Sent me on a bit of a wild goose chase.

[dd32]

In 41599:

Embeds: Switch the Imgur oEmbed endpoint to use SSL as the HTTP version has been deprecated.

Props swissspidy.
Fixes #41984.

[GunGeekATX]

Thanks. Related to this, Imgur also has albums and galleries which can be embedded. I've added these to the current project I'm working on (which is how I noticed the https issue). I can open a new ticket and patch if sounds like something that should be supported in core.

// Add providers for albums and galleries.
$providers['#https?://(.+\.)?imgur\.com/a/.*#i'] = array(
	'https://api.imgur.com/oembed',
	true,
);

$providers['#https?://(.+\.)?imgur\.com/gallery/.*#i'] = array(
	'https://api.imgur.com/oembed',
	true,
);

Examples:
​https://imgur.com/a/frTsT
​https://imgur.com/gallery/11TsUHK

[dd32]

@GunGeekATX Albums and Galleries are both supported by the core regex :) Due to the HTTP breakage you probably didn't notice.
For reference, the existing regex '#https?://(.+\.)?imgur\.com/.*#i' captures all imgur subdomains and paths.

[GunGeekATX]

Replying to dd32:

@GunGeekATX Albums and Galleries are both supported by the core regex :) Due to the HTTP breakage you probably didn't notice.
For reference, the existing regex '#https?://(.+\.)?imgur\.com/.*#i' captures all imgur subdomains and paths.

Ah yes, it does indeed (.*). Thanks!