> i don't think so. You're wrong! Sorry don't mean to be rude but it seemed like you were being rude to me.
In an attempt to give you all the details of our problem we noticed that the headers were returning the original time stamp along with the same Etag. The Etag issue was caused by our Jboss server because the webdav servlet was reading the timestamp off of the node and sending it back with the old timestamp. This was my fault because I thought the time stamp would be updated automatically on an update...stupid me. Once I manually added the timestamp on a save the webdav servlet returned the correct header which told the browser to return the newly updated page. As much as I appreciate you trying to help me, please don't if you're going to automatically assume that the person requesting the help is making things up! Brett -----Original Message----- From: Angela Schreiber [mailto:[EMAIL PROTECTED] Sent: Tuesday, April 01, 2008 9:50 AM To: [email protected] Subject: Re: webdav caching Conoly, Brett wrote: > [...] but it or something else is > definitely sending headers telling the client to cache. i don't think so. > Does anyone know if there is a place to configure the servlet to send a > "no-cache header" you can't configure that for it's pretty uncommon that the server always sends a no-cache header... normally you want the client to be able to cache things as long as they haven't changed. if you want the servlet to ALWAYS send a no-cache header you have to overwrite the webdav-servlet and make sure the WebdavResponseImpl constructor is build with the 'noCache'=true -> always send a no-cache header. > Thanks for the response welcome angela
