AW: IDP3.2.1 Unable to decode incoming request

[Kevin Flückiger]

Hi Thomas

I had the exact same problem this morning. I'm not familiar with Jetty, but in my setup I have apache with an ajp Proxy in front of tomcat. Maybe you have such a Proxy as well?
If so, then place the favicon in the apache document root of your vhost. I cannot really say why it has to be like that, since I redirect all traffic to /idp where my proxy is configured, but it works like that.
Hope that helps!

Best Regards
Kevin

-----Ursprüngliche Nachricht-----
Von: users [mailto:users-bounces at shibboleth.net] Im Auftrag von Käfer Thomas
Gesendet: Montag, 18. Juli 2016 12:44
An: users at shibboleth.net
Betreff: AW: IDP3.2.1 Unable to decode incoming request

Hah!

A colleague of me tracked down the cause of the problem using fiddler:

The way I came up with to get our own favicon to show for the IDP by using a redrect (see previous message for details) made the Jetty server send a new JSESSIONID with the response to the favicon get request, and Firefox will overwrite the JSESSIONID from the first request with this, therefore the session gets lost.

How do other people get their own favicon into Jetty 9.3 with Shibboleth?

Kind Regards,
Thomas Käfer
-- 
To unsubscribe from this list send an email to users-unsubscribe at shibboleth.net