I assume you mean 304 (Not modified) instead of 404 (Not found). Simplest I can think of is to NOT put the "last-modified" header in your response. Then the browser won't send you an if-modified-since back.
On the other hand, if you can put a datestamp on the response - e.g. a file date or by reading it from a DB or so - provide the proper response and you get client-side caching for (almost) free, which can seriously reduce load on a server. M. > -----Original Message----- > From: Abid Hussain [mailto:abid.huss...@dilax.com] > Sent: woensdag 16 december 2009 14:11 > To: users > Subject: Ignore http header if-modified-since > > Hallo, > > when processing ajax-requests Tomcat sometimes responds with > a 404 instead of delivering XML. > > This seems to happen when the http header "if-modified-since" > in the request doesn't somehow contain "the right" value. At > least, if the request doesn't contain this header, tomcat > responds "correctly". > > Is it possible to instruct tomcat to simply ignore this > header so that the correct response will be delivered, > whatever is contained in this header? > > Best regards, > > Abid (EOF) This message and attachment(s) are intended solely for use by the addressee and may contain information that is privileged, confidential or otherwise exempt from disclosure under applicable law. If you are not the intended recipient or agent thereof responsible for delivering this message to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please notify the sender immediately by telephone and with a 'reply' message. Thank you for your co-operation. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
