Bug 51224 - mod_dav_fs should respect FileETag
Summary: mod_dav_fs should respect FileETag
Alias: None
Product: Apache httpd-2
Classification: Unclassified
Component: mod_dav (show other bugs)
Version: 2.2.14
Hardware: PC Linux
: P2 normal (vote)
Target Milestone: ---
Assignee: Apache HTTPD Bugs Mailing List
Keywords: MassUpdate
Depends on:
Reported: 2011-05-18 21:17 UTC by Joel Ebel
Modified: 2018-11-07 21:10 UTC (History)
2 users (show)


Note You need to log in before you can comment on or make changes to this bug.
Description Joel Ebel 2011-05-18 21:17:11 UTC
Apache core allows configuration of the etag with the FileETag directive.  This is particularly important to us due to having multiple backends, where the inode will be different depending on which backend is used.  As a result we do not want the inode to be part of our etag.  Unfortunately, mod_dav_fs does not respect the FileETag directive, and always includes the inode as part of the etag.  This causes a problem for davfs2, which uses etags to determine if a cached file is still valid.  davfs retrieves files with a GET, which uses the etag defined by the core, but when doing a directory listing, uses PROPFIND, which uses the mod_dav_fs etag, which is then different.  This invalidates the cache of every file on every directory listing.  mod_dav_fs should respect the FileETag directive so that these etags match.
Comment 1 Michael Haro 2011-05-18 22:18:40 UTC
The use case for this bug is multiple servers using DAV with read-only files behind a load balancer.
Comment 2 William A. Rowe Jr. 2018-11-07 21:10:03 UTC
Please help us to refine our list of open and current defects; this is a mass update of old and inactive Bugzilla reports which reflect user error, already resolved defects, and still-existing defects in httpd.

As repeatedly announced, the Apache HTTP Server Project has discontinued all development and patch review of the 2.2.x series of releases. The final release 2.2.34 was published in July 2017, and no further evaluation of bug reports or security risks will be considered or published for 2.2.x releases. All reports older than 2.4.x have been updated to status RESOLVED/LATER; no further action is expected unless the report still applies to a current version of httpd.

If your report represented a question or confusion about how to use an httpd feature, an unexpected server behavior, problems building or installing httpd, or working with an external component (a third party module, browser etc.) we ask you to start by bringing your question to the User Support and Discussion mailing list, see [https://httpd.apache.org/lists.html#http-users] for details. Include a link to this Bugzilla report for completeness with your question.

If your report was clearly a defect in httpd or a feature request, we ask that you retest using a modern httpd release (2.4.33 or later) released in the past year. If it can be reproduced, please reopen this bug and change the Version field above to the httpd version you have reconfirmed with.

Your help in identifying defects or enhancements still applicable to the current httpd server software release is greatly appreciated.