=?gb2312?B?tPC4tDogbW9kX2F1dGhfY2FzIHdpdGggQ0FTIDMuMw==?=

[lobatt]

Thank you Phil, that's the right fix.
I am so sorry for bothering the list with this amateur question.
Best wishes,

Li Cheng
-----ÓʼþÔ­¼þ-----
·¢¼þÈË: cas-bounces at tp.its.yale.edu [mailto:cas-bounces at tp.its.yale.edu] ´ú
±í Phil Ames
·¢ËÍʱ¼ä: 2008Äê10ÔÂ16ÈÕ 19:57
ÊÕ¼þÈË: Yale CAS mailing list
Ö÷Ìâ: Re: mod_auth_cas with CAS 3.3

Hi,
Can you try changing "Directory" to "Location" and see if that fixes
the problem?  If I recall correctly, Directory applies to file system
directories whereas Location applies to URLs off the DocumentRoot.

-Phil

On Thu, Oct 16, 2008 at 1:03 AM, lobatt <lobatt at 163.com> wrote:
> Dear list:
>
>  I am now deploying a CAS 3.3 server in my test environment, and now I
> encountered a problem:
>
> I used mod_auth_cas as my CAS Client, and configured it in my httpd.conf
> like below:
>
> LoadModule auth_cas_module modules/mod_auth_cas.so
>
> CASCookiePath /tmp/cas/
>
> CASloginURL https://localhost/cas/login
>
> CASValidateURL https://localhost/cas/serviceValidate
>
> CASCertificatePath /home/user/common/httpd-2.0.59/conf/localhost.crt
>
> <Directory "/casprotect/">
>
> AuthType CAS
>
> Require valid-user
>
> </Directory>
>
>
>
> But the casprotect directory just not being protected by CAS, but if I
> change "/casprotect/" into "/", then, the protection will be there and
> redirect my request to the CAS login screen. But that's not what I want,
> there must be some thing wrong, would you please help me figure it out?
>
>
>
> --
>
> Li Cheng
>
> Computer Center
>
> Peking University
>
> 2008-10-15
>
>
> _______________________________________________
> Yale CAS mailing list
> cas at tp.its.yale.edu
> http://tp.its.yale.edu/mailman/listinfo/cas
>
_______________________________________________
Yale CAS mailing list
cas at tp.its.yale.edu
http://tp.its.yale.edu/mailman/listinfo/cas