Protect svn files in .htaccess
Uwe Hermann - August 12, 2005 - 21:04
| Project: | Drupal |
| Version: | 5.x-dev |
| Component: | base system |
| Category: | feature request |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | closed |
Description
The provided patch adds some more files and directories which will be protected by the default Drupal .htaccess file.
First, lots of files and directories used by Subversion (svn), as I keep all my Drupal installations under version control (and Drupal might switch to svn later, too). The database/ directory and *.mysql and *.pgsql, because nobody needs to access those from the web. I removed the update/ directory from the list, there's no such directory in CVS or 4.6., so I guess it's obsolete.
| Attachment | Size |
|---|---|
| htaccess_4.patch | 895 bytes |
#1
For me .htaccess directory blocking is broken. directory/ is blocked, while directory/file.txt is not. It's clearly ineffective.
#2
No patch attached.
#3
-1. When and if Drupal ever uses svn, it'll add this stuff in - until then, it shouldn't cater to your environment. As for database/, it's as innocent as someone requesting CHANGELOG.txt, and has no reason for being blocked. The only thing worthwhile from this patch is the removal of updates - because that's already covered with the .inc. Note: this has nothing to do with directories, only [Files].
Marking as duplicate, see final patch/revisions at http://drupal.org/node/29344.
#4
OK, you're probably right. Marking as postponed.
#5
subscribing
#6
Agreed that SVN directories and files should be blocked. (Possibly even backport to Drupal 6.x).
#7
New patch against HEAD. Note that the original patch included mostly directories - Apache's FilesMatch (or Files) have never worked against directories. From the original patch, only .svn-base, entries, and format are valid. Also included in this patch is "all-wcprops".
#8
Correcting typo.
#9
Reroll
#10
A lot of us already use SVN to manage Drupal sites. I'm for this to go in right now.
#11
Committed to CVS HEAD. Thanks.
#12
Automatically closed -- issue fixed for two weeks with no activity.
#13
Patch for Drupal 6.
#14
Looks good to me, pending on feedback from http://lists.drupal.org/pipermail/development/2008-November/031378.html
#15
Thanks, committed to Drupal 6 given no further pressing needs coming up from that thread. Moving to 5.x.
#16
Committed to 5.x.
#17
Automatically closed -- issue fixed for two weeks with no activity.