> The Tomcat 3.2 standalone does not seem to support http status code 304 > ('if-modified-since', code SC_NOT_MODIFIED) and is always sending back the > entire file, even it has not been modified. > > Is it going to be supported by versions '3.3' or 4.0 ? All HTTP/1.1 ifs headers should be supported in 4.0, as well as ranged requests (for resuming), and many other things. If you're using TC in standalone mode, I would recommend upgrading to 4.0 beta 2 when it's released. Remy --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
- Re: Tomcat Setup and configu... Mel Martinez
- Re: Tomcat Setup and configu... cmanolache
- Re: Tomcat Setup and configu... Mel Martinez
- Re: Tomcat Setup and configu... cmanolache
- Re: Tomcat Setup and configu... Mel Martinez
- Re: cvs commit: jakarta-tomcat-4... Glenn Nielsen
- Re: cvs commit: jakarta-tomc... Mel Martinez
- Re: cvs commit: jakarta-tomc... Glenn Nielsen
- Re: cvs commit: jakarta-tomc... cmanolache
- Any plan to support status 304 ? Tal Dayan
- RE: Any plan to support status 304 ? Remy Maucherat
- RE: Any plan to support status 304 ? Tal Dayan
- Re: Any plan to support status 304 ? Craig R. McClanahan
- cvs commit: jakarta-tomcat-4.0/jasper/src/share/org/ap... glenn
- cvs commit: jakarta-tomcat-4.0/jasper/src/share/org/ap... kinman
- cvs commit: jakarta-tomcat-4.0/jasper/src/share/org/ap... kinman