GoFuckYourself.com - Adult Webmaster Forum - View Single Post - DMCA: Why do CDN's think they are above the law?

Konda · 03-17-2017, 05:14 AM

The content is on the client's origin server, this is not with the CDN network.

For example our servers are with Reflected but we use LimeLight for CDN.
When a file is requested for the first time the LimeLight CDN node that the customer reaches requests the file from the server at Reflected and then stores it temporarily on the CDN (cache), so when the file is requested again by a user from the same region he get's it much faster as it comes from a server close to him. If the file is not requested from that same node for say 24 hours (depending on the expiry the client sets) it is removed again.

If you contact the CDN provider to get a file removed there is not much they can do. The file could be present on 100s of different CDN nodes where it's temporarily stored. If they would somehow delete it (not really possible, but hypothetically) and a visitor would request it again it would be back on the node as it would just get it from the origin server again.

So yeah the CDN providers are correct that they can't delete the files, it has to be deleted from the origin server (which could be any host). There is nothing a CDN provider can do.

03-17-2017, 05:14 AM
Konda ... Industry Role: Join Date: Apr 2003 Posts: 2,280	The content is on the client's origin server, this is not with the CDN network. For example our servers are with Reflected but we use LimeLight for CDN. When a file is requested for the first time the LimeLight CDN node that the customer reaches requests the file from the server at Reflected and then stores it temporarily on the CDN (cache), so when the file is requested again by a user from the same region he get's it much faster as it comes from a server close to him. If the file is not requested from that same node for say 24 hours (depending on the expiry the client sets) it is removed again. If you contact the CDN provider to get a file removed there is not much they can do. The file could be present on 100s of different CDN nodes where it's temporarily stored. If they would somehow delete it (not really possible, but hypothetically) and a visitor would request it again it would be back on the node as it would just get it from the origin server again. So yeah the CDN providers are correct that they can't delete the files, it has to be deleted from the origin server (which could be any host). There is nothing a CDN provider can do.