idp metadata mimetype

[Chad La Joie]

Returning the document with the application/samlmetadata+xml MIME type
prevents it from being rendered in a browser.  So the code was changed
so that if a client made a proper HTTP request and listed that MIME
type as being supported than the response would indicate the same MIME
type in the response.  Otherwise it would be returned as text/xml.

Technically, the way it should work, is that clients should list the
SAML metadata MIME type as the accepted encoding format in the request
and any other request should be returned an HTTP 406 (Not Acceptable)
status code.  Such a strict adherence doesn't seem like a benefit to
anyone in my opinion, however.

On Thu, Dec 15, 2011 at 15:05, Liam Hoekenga <liamr at umich.edu> wrote:
> We recently upgraded our IdP from 2.1.5 to 2.3.5, and I've noticed
> that the mimetype of the IdP's metadata has changed from
> application/samlmetadata+xml to application/xml (this also involved a
> tomcat and java upgrade..)
>
> One of our system monitoring tests is looking specifically for
> application/samlmetadata+xml.. I could request that the test look for
> a different mimetype, but since I control the IdP, I thought it might
> be faster for me to change it on my side.
>
> I see you can set the mimetype of the metadata in the SP.
> Is it possible to specify the mimetype of the metadata for the IdP?
>
> Liam
>
>
>
>
> --
> To unsubscribe from this list send an email to users-unsubscribe at shibboleth.net



-- 
Chad La Joie
www.itumi.biz
trusted identities, delivered