Received: (qmail 16674 invoked by uid 2012); 5 Dec 1998 19:26:12 -0000 Message-Id: <19981205192612.16673.qmail@hyperreal.org> Date: 5 Dec 1998 19:26:12 -0000 From: Sven Carstens Reply-To: carstens@rbi.informatik.uni-frankfurt.de To: apbugs@hyperreal.org Subject: Last-Modified Date set to 1.1.1970 X-Send-Pr-Version: 3.2 >Number: 3497 >Category: mod_cgi >Synopsis: Last-Modified Date set to 1.1.1970 >Confidential: no >Severity: non-critical >Priority: medium >Responsible: apache >State: closed >Class: sw-bug >Submitter-Id: apache >Arrival-Date: Sat Dec 5 11:30:00 PST 1998 >Last-Modified: Sat Dec 5 13:20:00 PST 1998 >Originator: carstens@rbi.informatik.uni-frankfurt.de >Organization: >Release: 1.3.3 >Environment: Linux 2.0.35 i686 libc5 >Description: The script is not an nph-script. The script sets the Last-Modified field to the curent date/time. The header produced by the script is overwritten partially. The Last-Modified field is set to 1.1.1970. >How-To-Repeat: Sorry! Not yet Online. >Fix: >Audit-Trail: State-Changed-From-To: open-feedback State-Changed-By: marc State-Changed-When: Sat Dec 5 11:38:04 PST 1998 State-Changed-Why: You have to be more explicit about exactly what you are doing and exactly what you are seeing. Please send a script that demonstrates the problem. How are you determining that "the header is overwritten partially"? This really sounds like either your script or your method of determining the last-modified are broken and is unlikely to be an Apache problem. State-Changed-From-To: feedback-closed State-Changed-By: marc State-Changed-When: Sat Dec 5 12:08:41 PST 1998 State-Changed-Why: Your date format is incorrect. You can't just make up a format. As the HTTP spec defines, the following formats: Sun, 06 Nov 1994 08:49:37 GMT ; RFC 822, updated by RFC 1123 Sunday, 06-Nov-94 08:49:37 GMT ; RFC 850, obsoleted by RFC 1036 Sun Nov 6 08:49:37 1994 ; ANSI C's asctime() format have been historically valid and are accepted, althoug the first is the only one that should be generated. From: Sven Carstens To: marc@apache.org, apbugs@Apache.Org Cc: Subject: Re: mod_cgi/3497: Last-Modified Date set to 1.1.1970 Date: Sat, 05 Dec 1998 21:02:28 +0100 marc@apache.org wrote: > Please send a script that demonstrates the problem. > > How are you determining that "the header is overwritten partially"? > > This really sounds like either your script or your method > of determining the last-modified are broken and is unlikely > to be an Apache problem. Here is a little script that shows the problem. -------------------- script start #!/usr/bin/perl print < Test Page for Error

It Worked! (or not)

HTML -------------------- script end will result in the following output --------------------output start HTTP/1.1 200 OK Date: Sat, 05 Dec 1998 20:00:29 GMT Server: Apache/1.3.3 (Unix) Last-Modified: Thu, 01 Jan 1970 00:00:00 GMT Connection: close Content-Type: text/html Test Page for Error

It Worked! (or not)

---------------------output end CU sven From: Sven Carstens To: marc@apache.org, apbugs@Apache.Org Cc: Subject: Re: mod_cgi/3497: Last-Modified Date set to 1.1.1970 Date: Sat, 05 Dec 1998 21:58:56 +0100 marc@apache.org wrote: > Your date format is incorrect. You can't just make up a > format. As the HTTP spec defines, the following formats: > > Sun, 06 Nov 1994 08:49:37 GMT ; RFC 822, updated by RFC 1123 > Sunday, 06-Nov-94 08:49:37 GMT ; RFC 850, obsoleted by RFC 1036 > Sun Nov 6 08:49:37 1994 ; ANSI C's asctime() format > > have been historically valid and are accepted, althoug the first is the only > one that should be generated. I didn't make it up as such... It is perfectly correct but for the year..... It is a Y2K problem........ If I set the Year from 98 to 1998 it works perfectly......... Perl localtime returns only a 2 digit year if used in an array context...... But it returns a 4 digit year if used in a scalar context......... Sorry to bother you...... (Still trying to get something reproducable for the connection problem) CU Sven >Unformatted: [In order for any reply to be added to the PR database, ] [you need to include in the Cc line ] [and leave the subject line UNCHANGED. This is not done] [automatically because of the potential for mail loops. ] [If you do not include this Cc, your reply may be ig- ] [nored unless you are responding to an explicit request ] [from a developer. ] [Reply only with text; DO NOT SEND ATTACHMENTS! ]