On Thursday, 11 December 2014 at 12:52:40 UTC, Iain Buclaw via Digitalmars-d-announce wrote:
Though I'm not nearly getting anywhere near the transfer limit inplace
on my VPS.  So it's not something I worry about too much.

Me neither on my servers, but he is right to worry about this and on S3 he actually has to pay for the traffic. Virtual host providers usually have a mixed calculation so the other customers are paying for you :o.

Isn't LDC also S3 backed? Ah, github-cloud.

Anyhow, there has already been a lot of automated traffic in the past, so if you didn't notice until now, that probably won't change soon. Also see http://forum.dlang.org/post/icoinkfyrmlnetxao...@forum.dlang.org.

That's also a good opportunity to check your cache-control response headers. None of them actually allows HTTP proxy servers to cache your downloads.

GDC: vibe.d's defaults => increase max-age to 31557600 and add public
  Last-Modified: Thu, 19 Jun 2014 07:55:26 GMT
  Etag: "F06035B41260515B28AD8924021AB57F"
  Expires: Fri, 12 Dec 2014 20:59:38 GMT
  Cache-Control: max-age=86400

DMD: no cache-control => add a Cache-Control header
  Last-Modified: Wed, 15 Oct 2014 21:10:57 GMT
  ETag: "dfb0833009f3204e850a87bbd560da03"

LDC: github's default => add public
  Cache-Control: max-age=31557600
Content-Disposition: attachment; filename=ldc2-0.15.0-beta1-linux-x86_64.tar.xz
  Last-Modified: Fri, 14 Nov 2014 17:40:49 GMT
  ETag: "3322634a9958e6c959c8a70614d09818"


And there is always Incapsula, though I'm not sure whether they have an upper limit on the filesizes that they cache.

Reply via email to