andres@corrada.com wrote:
On Mon, May 22, 2000 at 03:10:59PM -0500, Jon Delheimer wrote:
Shane,
I made the changes you suggested to Image.py.
Here are the results:
Thursday, 11-May-00 16:21:32 GMT 1900/05/11 16:21:31 GMT -2197697908.0
I have stepped through the debugger with the call of ZPublisher.Zope('/path/to/image', d=1). Upon immediate entry into the ZPublisher/Test.py module I can set environ['IF_MODIFIED_SINCE'] to something reasonable such as 'Wednesday, March 15, 2000 19:02:17 GMT' and I get no error as I step through the code. This exonerates the Zope python code.
The question then remains who is producing the buggy If-Modified-Since that puts the date back to 1900. Does someone know how to trap the headers that are sent to Zope so they can be inspected?
One easy way is to visit /Control_Panel/manage_debug which shows you the details about each active connection, including your own. Another possibility is to create a DTML method called "req" in your root folder which simply calls <dtml-var REQUEST>. I solved the 1900 problem by changing DateTime.py so that years 00-69 are now translated to 2000-2069. That's the way it was supposed to work in the first place; I think something fell through the cracks awhile back. Everybody is counting on having 64-bit processors or better by the year 2038, and if we do, performing an int() cast will be a safe thing to do. Shane