Message254249
I assume it affects Python 3, though I suspect the exception is OSError, not ValueError. But it would be good if someone with Windows (or other affected OS) could confirm.
I think the server should serve the file, with just a best-effort attempt to serve the timestamp. Some other options:
* Maybe using datetime rather than the OS’s gmtime() would be more reliable
* Omit the Last-Modified header if the timestamp cannot be represented
* Make time.gmtime() more platform-independent (probably against the original spirit of the module)
I don’t think setting Last-Modified to the current time is a particularly good idea. I guess omitting the field would have a similar effect on caching, without actually serving a misleading value. |
|
Date |
User |
Action |
Args |
2015-11-07 01:41:26 | martin.panter | set | recipients:
+ martin.panter, terry.reedy, paul.moore, tim.golden, zach.ware, Sean.Wang, steve.dower, xiang.zhang |
2015-11-07 01:41:26 | martin.panter | set | messageid: <1446860486.89.0.311259933204.issue25534@psf.upfronthosting.co.za> |
2015-11-07 01:41:26 | martin.panter | link | issue25534 messages |
2015-11-07 01:41:25 | martin.panter | create | |
|