HTTP Authorization

[Damien Wetzel]

For Authorisations, why don't pass the requests to the backend 
for the matching URLs as HEAD requests with Cookie: or Authorisation: 
headers in it then if the backend sends 200, Varnish send back the cached
URL, if backend sends 403, the response is forwarded back to the enduser ?

Ask Bjørn Hansen writes:
 > 
 > On Feb 13, 2007, at 9:24, cripy wrote:
 > 
 > > Hello, I am curious to know whether anybody has had any success  
 > > with caching files with HTTP authorization and still authorizing  
 > > correctly.  I have tried to implement the following VLC:
 > 
 > I don't know if it can be done with VLC, but I'd like to point to the  
 > perlbal "re-proxy" feature (for potential inspiration to varnish).
 > 
 > The idea is that the proxy sends the request to the backend server,  
 > the backend server (typically a "smart" server with DB access and  
 > heavy memory footprint) authorizes the request and gives the proxy  
 > another URL.  The proxy then fetches the file from that URL  
 > (typically on a "dumb" server) and sends it to the client.
 > 
 > 
 >   - ask
 > 
 > -- 
 > http://develooper.com/ - http://askask.com/
 > 
 > 
 > _______________________________________________
 > varnish-misc mailing list
 > varnish-misc at projects.linpro.no
 > http://projects.linpro.no/mailman/listinfo/varnish-misc