Bug 26478 - mod_dav does not expose a method for setting the Dav:source property for files in the repository
Summary: mod_dav does not expose a method for setting the Dav:source property for file...
Alias: None
Product: Apache httpd-2
Classification: Unclassified
Component: mod_dav (show other bugs)
Version: 2.0.48
Hardware: All All
: P3 enhancement (vote)
Target Milestone: ---
Assignee: Apache HTTPD Bugs Mailing List
Keywords: MassUpdate
Depends on:
Reported: 2004-01-28 00:31 UTC by Marc Richards
Modified: 2018-11-07 21:09 UTC (History)
1 user (show)


Note You need to log in before you can comment on or make changes to this bug.
Description Marc Richards 2004-01-28 00:31:01 UTC
RFC 2518 Section 10.3 describes the Dav:source property as a means for exposing
the uri of the source resource (as opposed to the output resource) of a given
entity i.e. the source code of a .php file as opposed to the html that it generates.

It would be great if mod_dav had a directive that could be specified in
httpd.conf to set the Dav:source URI for a given set of files.


AliasMatch ^/dav/(\w*)\.php /dav/$1\.php-src

<LocationMatch /dav/\w*\.php-src>
  Require valid-user

DAVSourceMap ^/dav/(\w*)\.php /dav/$1\.php-src

This would allow a WebDAV client to automatically determine which file to "GET"
depending on whether the user wanted to view or edit the file.
Comment 1 Marc Richards 2004-01-28 21:20:40 UTC

I should have added "ForceType text/plain" to the <LocationMatch> tag.

Comment 2 William A. Rowe Jr. 2018-11-07 21:09:26 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.