RE: I would like to know what tomcat release bug 345 was deferred to, still doesn't seem to be fixed on tomcat 3.2.3
Basically, there just wasn't time in the 3.2.2 release schedule to get this one fixed. Tomcat 3.2.3 was released earlier than planned due to a security problem and this bug hadn't been addressed yet. If someone would like to post a patch I will review and commit it. Marc Saegesser -Original Message- From: Stephen Dittmer [mailto:[EMAIL PROTECTED]] Sent: Thursday, July 26, 2001 10:34 AM To: '[EMAIL PROTECTED]'; '[EMAIL PROTECTED]' Cc: Henry Yeh; Irene Pan; Jack Egan; Wayne Tang Subject: I would like to know what tomcat release bug 345 was deferred to, still doesn't seem to be fixed on tomcat 3.2.3 I would like to know the status of this bug and what release it is going to be addressed in ? I found another person had filed bug 345 quite awhile back. We need the proper date header response back to browser so it won't reload staic files all the time. We don't want to use the IIS redirect as a way around this. This issue did not seem to get fixed/addressed in tomcat 3.2.3 which we just tried out. Here is a description of bug #345. Their is no date header in the Tomcat generated response, this is critical in case Tomcat is not running behind Apache e.g. According to the HTTP specs (RFC 2616) the Date header MUST be included by the origin server. --- Additional Comments From Marc Saegesser mailto:[EMAIL PROTECTED] 2001-03-21 11:46 --- This won't be addressed for Tomcat 3.2.2 but will be evaluated for a later release.
RE: I would like to know what tomcat release bug 345 was deferred to, still doesn't seem to be fixed on tomcat 3.2.3
I posted one yesterday, for TC 3.2.3 and TC 3.3 !: - Henri Gomez ___[_] EMAIL : [EMAIL PROTECTED](. .) PGP KEY : 697ECEDD...oOOo..(_)..oOOo... PGP Fingerprint : 9DF8 1EA8 ED53 2F39 DC9B 904A 364F 80E6 -Original Message- From: Marc Saegesser [mailto:[EMAIL PROTECTED]] Sent: Friday, July 27, 2001 3:46 PM To: [EMAIL PROTECTED] Subject: RE: I would like to know what tomcat release bug 345 was deferred to, still doesn't seem to be fixed on tomcat 3.2.3 Basically, there just wasn't time in the 3.2.2 release schedule to get this one fixed. Tomcat 3.2.3 was released earlier than planned due to a security problem and this bug hadn't been addressed yet. If someone would like to post a patch I will review and commit it. Marc Saegesser -Original Message- From: Stephen Dittmer [mailto:[EMAIL PROTECTED]] Sent: Thursday, July 26, 2001 10:34 AM To: '[EMAIL PROTECTED]'; '[EMAIL PROTECTED]' Cc: Henry Yeh; Irene Pan; Jack Egan; Wayne Tang Subject: I would like to know what tomcat release bug 345 was deferred to, still doesn't seem to be fixed on tomcat 3.2.3 I would like to know the status of this bug and what release it is going to be addressed in ? I found another person had filed bug 345 quite awhile back. We need the proper date header response back to browser so it won't reload staic files all the time. We don't want to use the IIS redirect as a way around this. This issue did not seem to get fixed/addressed in tomcat 3.2.3 which we just tried out. Here is a description of bug #345. Their is no date header in the Tomcat generated response, this is critical in case Tomcat is not running behind Apache e.g. According to the HTTP specs (RFC 2616) the Date header MUST be included by the origin server. --- Additional Comments From Marc Saegesser mailto:[EMAIL PROTECTED] 2001-03-21 11:46 --- This won't be addressed for Tomcat 3.2.2 but will be evaluated for a later release.
RE: I would like to know what tomcat release bug 345 was deferred to, still doesn't seem to be fixed on tomcat 3.2.3
I would like to know the status of this bug and what release it is going to be addressed in ? I found another person had filed bug 345 quite awhile back. We need the proper date header response back to browser so it won't reload staic files all the time. We don't want to use the IIS redirect as a way around this. This issue did not seem to get fixed/addressed in tomcat 3.2.3 which we just tried out. You're rigth, TC 3.2.3 and 3.3b1 didn't send the Date header. Who's is commiters agree to add the Date headers in both http connectors ? There is a hack in Date stuff which will avoid spending too much time to generate the date !: Here is a description of bug #345. Their is no date header in the Tomcat generated response, this is critical in case Tomcat is not running behind Apache e.g. According to the HTTP specs (RFC 2616) the Date header MUST be included by the origin server. --- Additional Comments From Marc Saegesser mailto:[EMAIL PROTECTED] 2001-03-21 11:46 --- This won't be addressed for Tomcat 3.2.2 but will be evaluated for a later release.
