Page History

...

Note that while this directive should work in DAV, its use there is discouraged; using this directive in WebDAV would open your source code and files to be viewable, downloadable and editable to the world.

Opening Access Without require noprompt

If for some reason you wish to open access without the use of require noprompt and/or to bypass CUWA all together, there is a method that allows this to be done via htaccess. However, it will also disable by default any standard authentication you add via htaccess for any subdirectories of the opened directory unless you take extra steps, so use with care. For most cases, require noprompt should do what you need without lots of interesting side effects. For the rest of the time, there's Satisfy.

In the directory you wish to open, create an .htaccess with:

Satisfy any
Allow from all
Order allow,deny

This configuration - in particular, Satisfy any - will bypass CUWA altogether, including NetID logging (even for logged-in users and subdirectories of a "require noprompt"). Allow from all and Order allow,deny are there to ensure that any higher level Allow/Order configurations aren't inherited and place similar restrictions. For any subdirectories of this opened directory, you will need to add the line

Satisfy all

to cause any CUWA htaccess-based restrictions to be picked up once again.

Note that using Satisfy in combination with Allow/Order/Require can cause interesting and unusual auth behaviors, particularly if you are using several layers of htaccess. For most intents and purposes, require noprompt should do what you need (i.e. open access to those without Cornell NetIDs). If you need or choose to use this method, though, it is strongly advisable to at least be familiar with the Satisfy directive and how it works.

httpd.apache.org - Satisfy (Apache 2.2)
httpd.apache.org - Allow (Apache 2.2)
httpd.apache.org - Order (Apache 2.2)

More information on CUWA Access Control

...