If someone opens a JIRA issue we can also add to the default supported list.
On Fri, Jul 25, 2008 at 9:35 AM, Scott Battaglia <[EMAIL PROTECTED]> wrote: > Its not hard-coded, not reliant on specific versions and its easily > configurable in code. The reason for its existence can be seen in this JIRA > issue: > > http://www.ja-sig.org/issues/browse/CAS-638 > > The issue is also open for improvements to filtering so if you have > different idea please feel free to share ;-) > > -Scott > > -Scott Battaglia > PGP Public Key Id: 0x383733AA > LinkedIn: http://www.linkedin.com/in/scottbattaglia > > On Fri, Jul 25, 2008 at 9:25 AM, Michael Ströder <[EMAIL PROTECTED]> > wrote: > >> Ronald Dai wrote: >> > I think I have found the cause. There is a supportedBrowser list in the >> > spnego code. It supports MSIE, Firefox, AppleWebKit, and SeaMonkey is >> > not in this list. So I think this issue can be resolved by adding the >> > SeaMonkey into this list. Could anyone confirm it? Thanks! >> >> Aaargh! Ronald, you're right! It works when tweaking User-Agent header >> e.g. with http://prefbar.mozdev.org. >> >> When was this added to cas-server? Handling HTTP requests differently >> depending on User-Agent header really sucks. That's bad practice! I'd >> strongly vote for disabling this supportedBrowser check completely! >> >> Ciao, Michael. >> _______________________________________________ >> Yale CAS mailing list >> [email protected] >> http://tp.its.yale.edu/mailman/listinfo/cas >> > >
_______________________________________________ Yale CAS mailing list [email protected] http://tp.its.yale.edu/mailman/listinfo/cas
