Hi Sandesh, are you sure..? I don't think these are related. Either you do server validation (e-tag + lastmodified headers) or you expiry cache (expiry + cache control). It should not be necessary to also set cache-control, unless it is already set to no-cache..
Lars On Wed, Oct 22, 2014 at 10:50 AM, Sandesh Sukumar Doolipeta < [email protected]> wrote: > Hi Morten , > > Apologies for the delayed response. From the change you have made , > we are getting the E-Tag header. However , since the response headers do > not contain the "Cache-control" header , the browser depends on the client > to set the "If-none-match" header. In which case , the client has to store > the previous E-Tag value and send the "If-none-match" header. > > In the change that we had made , along with the "E-Tag" header , we > were also sending the "Cache-control: max-age=1" header. In this case , the > browser itself takes the responsibility of setting the "If-none-match" > header , instead of depending on the client. > > Is it possible to send the "Cache-control: max-age=1" header along with > the E-Tag header ? > > > On Mon, Oct 20, 2014 at 6:37 PM, Lars Helge Øverland <[email protected]> > wrote: > >> Good. I think this will work equally well. >> >> Lars >> >> > > > -- > *Sandesh Doolipeta**Application Developer* > [email protected] > Telephone9686062727 > [image: ThoughtWorks] <http://www.thoughtworks.com/> >
_______________________________________________ Mailing list: https://launchpad.net/~dhis2-devs Post to : [email protected] Unsubscribe : https://launchpad.net/~dhis2-devs More help : https://help.launchpad.net/ListHelp
