Hi, the file is contained in a jar (which is naturally in classpath) and inside this jar contained in the following path: <jar-file>/META-INF/progressbar/script.js
Best regards, Abid -----Ursprüngliche Nachricht----- Von: Pid [mailto:p...@pidster.com] Gesendet: Donnerstag, 17. Dezember 2009 14:20 An: users@tomcat.apache.org Betreff: Re: AW: RE: Ignore http header if-modified-since On 17/12/2009 11:26, Abid Hussain wrote: > Hallo, > > unfortunately it is a 404. And the 404 is only delivered when the > request header contains "if-modified-since". If not the request is > respondec correctly. This behaviour is reproducable. > > Below you find an example of failed and successful request. > The GET URL is in both cases > http://localhost:8080/mywebapp/faces/static/META-INF/progressbar/scrip > t.js The file is actually in a META-INF directory? p > --> Failed Request (means tomcat responds with 404): > Host: localhost:8080 > User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; de; rv:1.9.1.6) > Gecko/20091201 Firefox/3.5.6 (.NET CLR 3.5.30729) > Accept: > text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8 > Accept-Language: de-de,en-us;q=0.8,de;q=0.6,en;q=0.4,fr-fr;q=0.2 > Accept-Encoding: gzip,deflate > Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7 > Keep-Alive: 300 > Connection: keep-alive > Cookie: JSESSIONID=262FAFFC220AF50656BC67C1C1DD1331 > If-Modified-Since: Do, 17 Dez 2009 11:11:29 GMT > Cache-Control: max-age=0 > --> Response: > Server: Apache-Coyote/1.1 > Content-Type: text/html > Content-Length: 1093 > Date: Thu, 17 Dec 2009 11:24:38 GMT > > --> Successful: > Host: localhost:8080 > User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; de; rv:1.9.1.6) > Gecko/20091201 Firefox/3.5.6 (.NET CLR 3.5.30729) > Accept: > text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8 > Accept-Language: de-de,en-us;q=0.8,de;q=0.6,en;q=0.4,fr-fr;q=0.2 > Accept-Encoding: gzip,deflate > Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7 > Keep-Alive: 300 > Connection: keep-alive > Cookie: JSESSIONID=262FAFFC220AF50656BC67C1C1DD1331 > Cache-Control: max-age=0 > --> Response: > Server: Apache-Coyote/1.1 > Last-Modified: Do, 17 Dez 2009 11:11:29 GMT > Content-Type: text/javascript > Transfer-Encoding: chunked > Date: Thu, 17 Dec 2009 11:24:53 GMT > > Does anybody have an explanation for this? > > Best regards, > > Abid > > > -----Ursprüngliche Nachricht----- > Von: Looijmans, Mike [mailto:mike.looijm...@oce.com] > Gesendet: Mittwoch, 16. Dezember 2009 15:48 > An: Tomcat Users List > Betreff: RE: Ignore http header if-modified-since > > 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 > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org > For additional commands, e-mail: users-h...@tomcat.apache.org > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
