Avoid redirecting images in a custom instalation of Imgur

[malditogeek]

Fixes this very unfortunate bug https://github.com/gitterHQ/gitter/issues/798

[iparamonau]

Ouch!

The re-redirect plugin isn't the cause though. It's the Imgur's oEmbed endpoint that is messing it up. Re-direct was there for a reason, as Imgur wasn't returning proper data for direct image links. They still don't for GIFV files, for example, and it is important for us.

Your PR would remove all meta data, app embeds and GIFv support for direct file links :\

So. I just blacklisted oEmbed on i.stack.imgur.com domain and with this approach, your PR isn't required. The links are recognized just as files.
Here's the result with old code: http://iframely.com/debug?uri=http%3A%2F%2Fi.stack.imgur.com%2FDFn7t.jpg

You should be getting the same when your Iframely instance pulls newer version of whitelist.

Are there any other custom installation domains?

[Pokechu22]

There aren't any other custom installation domains as far as I can tell (and the SSL certificate only lists i.stack.imgur.com).

[iparamonau]

OK, so Imgur has fixed it on their side too: they just disabled oEmbed responses for Stack URLs.
http://api.imgur.com/oembed.json?url=http%3A%2F%2Fi.stack.imgur.com%2FDFn7t.jpg

So I guess we can close the PR now.

[malditogeek]

@iparamonau ah sweet, reverted the commit on our instance and it's working fine now. Cheers! 👍