Home > All Posts > Sort by Topic
Topic #340

Prevent hotlinking (aka bandwidth theft)

By Jack Hodgson | "Jack Hodgson" <reg008@...> | jghiii
July 16, 2004 | Post #340 | Topic #340

Thomas Scott, writing in A List Apart, proposes a clever way to block bandw= =3D idth theft, aka HotLinking. "...if someone tries to hotlink one of your = images, it'll fail =97 the browse=3D r, instead of receiving an image file, will receive the result of showpic= .php , which is =3D sent as text/ html . It'll realise it can't display it, and produce a brok= en image placeh=3D older. Bandwidth saved. "On the other hand, if someone tries to link = directly to your images, they'=3D ll get silently redirected to an HTML page with your credit on it! No red= X, no silly "deni=3D ed" image =97 just a handy page that shows them the image they want to se= e, and gives you=3D credit for your work. " I wonder if this could be reworked to protect v= ideos from hotlinking? I bet=3D it could. http://www.alistapart.com/articles/hotlinking/ http://www.jac= khodgson.com/weblog/ [View]



Re: Prevent hotlinking (aka bandwidth theft)

By Jack Hodgson | "Jack Hodgson" <reg008@...> | jghiii
July 16, 2004 | Post #341 | Topic #340

Sorry for the ugly formatting of my original posting. (How I hate Yahoo! Gr= =3D oups' software!) Here is my original, hopefully easier to read. ----- Th= omas Scott, writing in A List Apart, proposes a clever way to block bandw= =3D idth theft, aka HotLinking. "...if someone tries to hotlink one of your= images, it'll fail =97 the browse=3D r, instead of receiving an image file, will receive the result of showpic= .php , which is =3D sent as text/ html . It'll realise it can't display it, and produce a brok= en image placeh=3D older. Bandwidth saved. "On the other hand, if someone tries to link di= rectly to your images, they'=3D ll get silently redirected to an HTML page with your credit on it! No red= X, no silly "deni=3D ed" image =97 just a handy page that shows them the image they want to se= e, and gives you=3D credit for your work. " I wonder if this could be reworked to protect = videos from hotlinking? I bet=3D it could. http://www.alistapart.com/articles/hotlinking/ http://www.j= ackhodgson.com/weblog/ [View]



Re: Prevent hotlinking (aka bandwidth theft)

By Jack Hodgson | "Jack Hodgson" <reg008@...> | jghiii
July 16, 2004 | Post #342 | Topic #340

I surrender. Sorry. There's good stuff in there, I promise. [View]



Re: [videoblogging] Prevent hotlinking (aka bandwidth theft)

By Lucas Gonze | Lucas Gonze <lgonze@...> | lucas_gonze
July 16, 2004 | Post #343 | Topic #340

--0-160645103-1089998824=:9726 Content-Type: TEXT/PLAIN; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: QUOTED-PRINTABLE It's trivial to work around a referrer test. All you will accomplish with = this is to ensure that your work goes unwatched. As a side note, calling = people thieves is much more unkind than the situation calls for. On Fri,= 16 Jul 2004, Jack Hodgson wrote: > Thomas Scott, writing in A List Apart,= proposes a clever way to block bandw=3D > idth theft, > aka HotLinking. > = > "...if someone tries to hotlink one of your images, it'll fail =97 the br= owse=3D > r, instead of > receiving an image file, will receive the result = of showpic.php , which is =3D > sent as text/ > html . It'll realise it can= 't display it, and produce a broken image placeh=3D > older. > Bandwidth sa= ved. > > "On the other hand, if someone tries to link directly to your imag= es, they'=3D > ll get silently > redirected to an HTML page with your credi= t on it! No red X, no silly "deni=3D > ed" image =97 > just a handy page th= at shows them the image they want to see, and gives you=3D > credit > for y= our work. " > > I wonder if this could be reworked to protect videos from h= otlinking? I bet=3D > it could. > > http://www.alistapart.com/articles/hotl= inking/ > > http://www.jackhodgson.com/weblog/ > > > >... [View]



Re: [videoblogging] Prevent hotlinking (aka bandwidth theft)

By Adrian Miles | Adrian Miles <adrian.miles@...> | adrianlmiles
July 22, 2004 | Post #383 | Topic #340

On 17/07/2004, at 3:27 AM, Lucas Gonze wrote: > It's trivial to work around a referrer test. All you will accomplish > with > this is to ensure that your work goes unwatched. embedding this as an argument within a movie would be much more reliable, *if* you wanted to go down this particular path. > > As a side note, calling people thieves is much more unkind than the > situation calls for. indeed. but the issue is not black and white. linking to my stuff, fine. making a movie that embeds my movie, with appropriate recognition/citation etc, fine. embedding my movie with no acknowledgement so that you use my work as yours. that's not ok. but paying attention to referrers in your logs should identify this if it is a problem. cheers Adrian Miles ................................................................. hypertext.rmit || hypertext.rmit.edu.au/adrian interactive networked video || hypertext.rmit.edu.au/vog research blog || hypertext.rmit.edu.au/vog/vlog/ [View]