Dingwell, Robert A. wrote:
Amos,

Thanks for the suggestion but I thought offline_mode would not attempt to access the origin server and would merely return the cached content that it has, is this correct? If so is there a way to override its behaviour to serve from the cache just when the origin is down?

Essentially what I would like is for squid to cache everything and serve up the cache when the origin is down. Even though this is all contained on our own wan attempting to get everyone to set the stale-if-error header is too difficult . We have a number of RESTful services that other services are dependent on and when those REST services are unavailable we still want to have the other services that depend on that data to function properly, even if it means the potential of using stale data.
Thanks

Rob Dingwell


I'm not exactly certain of the full behavior of offline_mode.
I do know that its not a true offline, but does aggressive caching like you asked for.

Some testing is in order to see if it meets your needs or not. Until a better version comes along.

Amos



On 3/20/09 10:11 PM, "Amos Jeffries" <squ...@treenet.co.nz> wrote:

    Dingwell, Robert A. wrote:
    >  Does anybody know if there is a way to do this?

    Try offline_mode on.
    Which is not a true offline, but an aggressive caching mode.

    Amos

    >
    >  Thanks
    >
    >  Rob
    >
    >
    >  On 3/18/09 3:59 PM, "Dingwell, Robert A." <b...@mitre.org> wrote:
    >
    > > Hi,
    > >
    > > I’m looking for a way to cache data from systems that are
    disconnected at
    > > times and to serve from the cache when the systems are
    disconnected.  I know
    > > that 2.7 supports the stale-if-error directive but I believe that
    requires
    > > the origin to set that in the content header which is currently
    out of the
    > > realm of possibilities.   Is there another way to do this?  Can I use
    > > header_replace to force the stale-if-error directive?
    > >
    > > Thanks
    > >
    > >
    >


    --
    Please be using
       Current Stable Squid 2.7.STABLE6 or 3.0.STABLE13
       Current Beta Squid 3.1.0.6



--
Please be using
  Current Stable Squid 2.7.STABLE6 or 3.0.STABLE13
  Current Beta Squid 3.1.0.6

Reply via email to