Details
-
Type:
Improvement
-
Status: Closed
-
Priority:
Minor
-
Resolution: Fixed
-
Affects Version/s: 2.5
-
Component/s: Files API
-
Labels:
-
Testing Instructions:
-
Affected Branches:MOODLE_25_STABLE
-
Fixed Branches:MOODLE_23_STABLE, MOODLE_24_STABLE, MOODLE_25_STABLE, MOODLE_26_STABLE
-
Pull from Repository:
-
Pull Master Branch:m26_
MDL-39832_Fix_Chrome_Issues_ETag_XSendfile_2ndRound
Description
See MDL-39688, this patch started to implement ETag headers based on HTTP ranges.
Further investigations have driven to another solution which should be applied to the branches where MDL-39688 has been applied because of the ETag header added by Moodle is content driven, helping browser caching mechanisms to work as expected even in cluster deployments where e.g. ETag being added by Apache+X-Sendifle could be built on top of file inodes, probably dependent on the web server serving the request even if files are shared ($CFG->dataroot) someway between all the nodes.