Closed (fixed)
Project:
Apps
Version:
7.x-1.x-dev
Component:
Code
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
21 Sep 2012 at 00:01 UTC
Updated:
4 Sep 2014 at 17:50 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #1
populist commentedThis patch will do a simple check to see if the last-modified value exists before doing checking against it. It also changes and documents the conditional logic so the "file" is altered if either information (last-modified or content-length) exists but is different than the original file.
Comment #2
elliotttf commentedIs there a chance that
$remote['last-modified']could legitimately be 0 (not necessarily intentionally, but perhaps due to server misconfiguration, etc) in which caseisset()should be used in favor ofempty()?That edge case aside this change makes sense and looks good to me.
Comment #3
populist commented@elliotttf - It is not possible for last-modified to be legitimately zero since the spec requires an HTTP-date (http://www.w3.org/Protocols/rfc2616/rfc2616-sec3.html#sec3.3.1) which cannot be zero.
Comment #4
mrfelton commentedSame patch, updated to apply against latest codebase
Comment #5
mrfelton commentedLeaving as RTBC, since this is just a straight reroll.
Comment #6
hefox commentedThat wasn't the straightiest of rerolls, populist have you tested it?
Comment #7
hefox commentedSeemed safe enough