e Mar 28 août 2007 21:39, Diego Woitasen a écrit : > The question is, how Squid act with the objects in an authenticated > environment. If some browser A get an object with authentication and then > is cached, what happen if a browser B request the same object? Is returned > from the cache or object that requieres authentication are never cached? The objects with authentication are never cached if : 1 - Squid doesn't have ignore-auth set in its configuration file AND 2 - The web server hasn't sent "Cache-Control: public" in the response header. If webserver sends "Cache-Control: public" (or ignore-auth is set), the first user downloading the object will require a valid authentication. Next users won't need authentication if object is cached. If webserver sends "Cache-Control: public, max-age=0", object is cached but all users will require a valid authentication to the end server. Regards, René