This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author terry.reedy
Recipients Sean.Wang, martin.panter, paul.moore, steve.dower, terry.reedy, tim.golden, xiang.zhang, zach.ware
Date 2015-11-07.00:50:51
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1446857452.0.0.474388571588.issue25534@psf.upfronthosting.co.za>
In-reply-to
Content
Does this affect 3.x also?  I would expect that it does.

The question for this issue is whether the program should stop on a gmtime error and say "I will not serve this file until you fix the modification time." or whether it should catch and workaround the problem and merely warn about the mtime.

For the latter, BaseHTTPServer could catch the gmtime error and use the current time instead.  Or SimpleHTTPServer could catch the exception and omit the Last Modified: header, if that is allowed.  I believe the purpose of this header is for caching, and the current time would say to replace any cached value.
History
Date User Action Args
2015-11-07 00:50:52terry.reedysetrecipients: + terry.reedy, paul.moore, tim.golden, martin.panter, zach.ware, Sean.Wang, steve.dower, xiang.zhang
2015-11-07 00:50:51terry.reedysetmessageid: <1446857452.0.0.474388571588.issue25534@psf.upfronthosting.co.za>
2015-11-07 00:50:51terry.reedylinkissue25534 messages
2015-11-07 00:50:51terry.reedycreate