www-apache-bugdb mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From c...@apache.org
Subject Re: general/4565: cgi that changes system time causes the cgi to die
Date Mon, 21 Jun 1999 19:12:51 GMT
[In order for any reply to be added to the PR database, you need]
[to include <apbugs@Apache.Org> in the Cc line and make sure the]
[subject line starts with the report component and number, with ]
[or without any 'Re:' prefixes (such as "general/1098:" or      ]
["Re: general/1098:").  If the subject doesn't match this       ]
[pattern, your message will be misfiled and ignored.  The       ]
["apbugs" address is not added to the Cc line of messages from  ]
[the database 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!     ]


Synopsis: cgi that changes system time causes the cgi to die

State-Changed-From-To: open-closed
State-Changed-By: coar
State-Changed-When: Mon Jun 21 12:12:49 PDT 1999
State-Changed-Why:

There is really nothing we can do about this.  By changing
the system time you're causing existing timers within the
interval of the change to expire immediately.  If your
script is just trying to change the time and then display
a confirmation, try doing this in two steps.  Try having
the script emit HTML that includes something like this in
the <HEAD> portion:

 <META HTTP-EQUIV="Refresh" CONTENT='5; URL="http:..url-of-confirmation-page"'>

and then close the output stream and change the time.  Most
browsers will load the confirmation page after five seconds
have passed, which should be enough for the first script
to have finished its work.

Thanks for using Apache!



Mime
View raw message