Re: want to allow or deny an URL based on a timestamp

[Sascha Ottolski]

Am Mittwoch 13 August 2008 00:02:07 schrieb Darryl Dixon - Winterhouse 
Consulting:
 4) Object expires and Varnish goes to fetch it from the backend,
 which of course returns 404 or whatever as the URL has expired.

Darryl,

thanks for your reply. This would of course be a straight forward 
approach, but in my case, it's vital that the objects live almost 
forever in the cache.


Cheers,

Sascha
___
varnish-misc mailing list
varnish-misc@projects.linpro.no
http://projects.linpro.no/mailman/listinfo/varnish-misc

Re: want to allow or deny an URL based on a timestamp

[Michael S. Fischer]

Nearly every modern webserver has optimized file transfers using
sendfile(2).  You're not going to get any better performance by shifting the
burden of this task to your caching proxies.

--Michael

On Tue, Aug 12, 2008 at 12:53 AM, Sascha Ottolski [EMAIL PROTECTED] wrote:

 Hi all,

 I'm certain that it's possible, but am not sure how to do it: I want to
 let my application create encrypted URLs, that are valid only for a
 specific amount of time. I guess with the help of embedded C and
 manually constructed hash keys this should be doable. Now I'm wondering
 if may be someone already has done something like this, or as other
 ideas to achieve this?

 My idea is basically inspired by a lighttpd module:
 http://trac.lighttpd.net/trac/wiki/Docs:ModSecDownload

 The workflow would be something like

 - decrpyt incoming URL
 - rewrite URL, extract timestamp
 - if not in range, send 404 (or what seems appropriate)
 - if timestamp is ok, set hash key
 - deliver object from cache or pull from backend


 Thanks for any pointer,

 Sascha
 ___
 varnish-misc mailing list
 varnish-misc@projects.linpro.no
 http://projects.linpro.no/mailman/listinfo/varnish-misc


___
varnish-misc mailing list
varnish-misc@projects.linpro.no
http://projects.linpro.no/mailman/listinfo/varnish-misc