Thanks for the info.  While trying to do some more troubleshooting
(such as Live HTTP Headers, as you suggested), the problem went away;
I suspect that I cleared a problematic cookie or cached object from my
browser, but I'm not sure.  I'll keep in mind the DirectoryIndex
workaround that you suggested, in case the problem happens again.

Josh Kelley

On 8/2/07, Ames, Phillip <[EMAIL PROTECTED]> wrote:
> Josh,
> There are some interesting "features" involving Apache and mod_dir (the
> one that implements DirectoryIndex).  When I was developing, I ran into
> problems like this and this is what I believe is happening.
>
> 1.  You request /private/
> 2.  mod_dir intercepts your request since it is for a directory and
> consults a list of things it will treat as Directory Indexes (in the
> order you specify them)
> 3. Mod_dir generates a subrequest from your original request and
> specifies a file(whatever your first DirectoryIndex is), and then sends
> your browser to it
> 4. Mod_auth_cas now takes effect (mod_dir has hooks before mod_auth_cas)
> and is given a resource, like /private/index.php
> 5. Mod_auth_cas performs the CAS redirect and authenticates you to that
> service, but that service may not exist (if your indexes are really HTL
> files, for instance) and you get a 404
>
> Alternatively, what could be happening since you mention refresh is that
> your browser could be re-transmitting the old (used up) ticket in the
> query string.  This will fail verification.
>
> Another issue could be how Firefox and IE handle cookies on responses
> like a 302 redirect.  Have you had the opportunity to use something like
> Live HTTP Headers in conjunction with CASDebug to see what is going back
> and forth in the case of each browser?
>
> When using mod_cas by Yale I had to set the DirectoryIndex in each
> directory that I wanted people to be able to access using the /path/
> notation to the proper name (e.g. "DirectoryIndex admin.php")
_______________________________________________
Yale CAS mailing list
[email protected]
http://tp.its.yale.edu/mailman/listinfo/cas

Reply via email to