Quote:
Originally Posted by ownedbycats
It's not very common; I usually fix them right away so I'm not sure how many I have were affected by them and most of the few that I checked actually had the images go 404/410 from accounts being deleted.
Here is another test case with a working image though. |
What I found was that if the HTTP Referer header is set to the same image URL, I can get an image from photobucket without watermarking.
That's not something we want to apply across the board to all images. For some sites that host images, the referer needs to be 'parent' page (FFF already does that)--which is how referer is supposed to work.
I could add optional code to do this, but the questions then are: a) Should it only be for photobucket? b) Should it be a configurable pattern so it can be applied for other sites, too? c) Is this really common enough to bother with? And d) Is this a general solution even for photobucket? Two is not a very large sample set.