Shibboleth Developers

["Scott Cantor" <>]

> This "fixes" the problem, in the sense that the Internet Explorer via 
> http route case now always comes up with the HTTP_SHIB_ATTRIBUTES as I 
> expected from using Firefox.
> 
> So, it kind of looks like in some sense Shibboleth is seeing the request 
> as a request in the http scheme on port 8446 (strictly impossible; that 
> port is SSL-protected), and defaults to not exporting the assertion.

That sounds likely. Basically, all the info about the request comes from the
Apache API, so if it says it's not SSL, it's not considered SSL. Many
problems like this end up being caused by Apache acting strange due to
config errors.

I will say that those prompts *do* cause some double requests at times that
seem to be a problem, and I don't know what I can do to fix them. I always
strongly urge uniform use of SSL. For testing of course, it doesn't much
matter.

-- Scott