Page History

...

If you wish to have ALL traffic protected by SSL we recommend that you request "HTTPS" for the protocol.  This will create a redirect so that any traffic that goes to http://\[my site]/ will be redirected to https://\[my site]/.

In some cases you may wish to only have a portion of your site protected by SSL while the option portion is not.  In this case if you specify "BOTH" then you will be responsible for determining whether a page can be displayed using SSL or non-SSL.

...

Note that if you protect a directory with CU WebAuth and you go to the non-SSL site you will get the following error "CUWebAuth error... Server is not properly configured. Check the Kerberos principal.". In this case you need to be sure to specify the "https" URL and not the "http" URL to avoid getting the error. If you wish to setup a redirect from the non-SSL site to the SSL site for the ".htaccess" protected directory you'll either need to specify the redirect in a parent directory or via a custom vhost virtualhost include.

Migrating from a "legacy" configuration

...

This will case a problem for new "HTTP" configurations since CUWebAuth is not loaded for non-SSL traffic. One possible fix is to remove "require noprompt" if you wish to have no CUWebAuth protection.  Note that special care should be taken to ensure that there are no directories beneath that were expecting cuwebauth to be enabled.  This can be tricky configuration to verify that there is no risk of exposing files that should be protected.

Example of a problem configuration #2 (require valid-user)

...