Looks like imgur banned wickedfire from hotlinking...

rish3

New member
May 21, 2011
1,003
23
0
Dallas, TX
Noticed this morning. Pictures you've seen before will show, since they are in your browser cache, but if you empty the cache, or hotlink a new image here, imgur will return a "403 forbidden".

Cut and paste the url of the image into a new browser window, and it shows...since the referrer url isn't wickedfire.com in that case.

Mods: A quick and dirty fix would be to search/replace i.imgur.com to x.imgur.com. That forces a 302 redirect and strips the referrer.

Example...

Hotlinked with i.imgur.com (won't show):
eWZXS.jpg


Hotlinked with x.imgur.com:
0NAfQ.jpg


If you can see both images, then perhaps it's just me...
 


cant imagine why they wouldnt want to host the nice content that we use imgur for
 
So who provides the next best thing? Or perhaps one of the WF coder's would like to take on a new business?

Edit: Perhaps imgur hasn't received enough email lately
 
Damn it

We had better attach the image with the post and link it. Just like this!

attachment.php
 

Attachments

  • chick.jpg
    chick.jpg
    50.2 KB · Views: 361
Note that if you try to hotlink an image yourself, it will appear to work, because when you uploaded it, the image went in your browser cache...nobody else will see it though.
 
Fuck it, just when I thought this place couldn't become a more dumbass shit hole not worth visiting, this shit happens
 
They didn't ban wickedfire, they're having issues with i.imgur.com on a bunch of other sites too. If you get rid of the i. part and just leave imgur.com the image hotlinks just fine.
 
They didn't ban wickedfire, they're having issues with i.imgur.com on a bunch of other sites too. If you get rid of the i. part and just leave imgur.com the image hotlinks just fine.

This sounds more plausible considering the amount of bandwidth deal with unless they're tired of the WF troll squad.
 
They didn't ban wickedfire, they're having issues with i.imgur.com on a bunch of other sites too. If you get rid of the i. part and just leave imgur.com the image hotlinks just fine.

Nope, they banned it:

Code:
$ curl -i --referer wickedfire.com http://i.imgur.com/eWZXS.jpg 2>>/dev/null | head -1
HTTP/1.1 403 Forbidden

$ curl -i --referer google.com http://i.imgur.com/eWZXS.jpg 2>>/dev/null | head -1
HTTP/1.1 200 OK

So we have to use 1 of the other 100 million image hosts now
Yeah, fine for new threads, but it does make a fair number of existing threads useless.