Cannot authenticate user using SeaMonkey browser

[Scott Battaglia]

-Scott Battaglia
PGP Public Key Id: 0x383733AA
LinkedIn: http://www.linkedin.com/in/scottbattaglia

On Fri, Jul 25, 2008 at 12:32 PM, Michael Ströder <michael at stroeder.com>
wrote:

> Michael Ströder wrote:
> > Scott Battaglia wrote:
> >> Its not hard-coded, not reliant on specific versions and its easily
> >> configurable in code.
> >
> > What do I have to add where to deployerConfigContext.xml?
> > How to switch it off?
> >
> >>  The reason for its existence can be seen in this JIRA issue:
> >>
> >> http://www.ja-sig.org/issues/browse/CAS-638
> >
> > This seems to me like misbehaving other browsers are the reason why
> > valid browsers fail now. :-(
>
> Since this might sound a little harsh I rephrase it:
> I'd prefer to maintain a black-list (unSupportedBrowser list) of
> misbehaving browsers not correctly ignoring unknown HTTP headers instead
> of having to maintain a white-list of well-behaving browsers
> (supportedBrowser list).


Haha I just suggested the same thing!  I'm waiting for our SPNEGO developer
to reply back to this list.

-Scott


>
>
> Ciao, Michael.
> _______________________________________________
> Yale CAS mailing list
> cas at tp.its.yale.edu
> http://tp.its.yale.edu/mailman/listinfo/cas
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://tp.its.yale.edu/pipermail/cas/attachments/20080725/4310d396/attachment.html