Subject: InCommon metadata support
- From: Ian Young <>
- Subject: Re: [Metadata-Support] MDQ format options?
- Date: Tue, 6 Dec 2016 21:13:55 +0000
- Feedback-id: 22.214.171.124
So yes, that's exactly how it is being determined. The browser says it prefers text/html, and that's one of the content types the implementation knows how to render, so that is what is returned. The content type is decided by this part of the configuration:
You can see the defaultContentType at the end there, which is used when the type isn't resolved, either because it hits a */* or in the case where no Accept header is sent.
This seemed like the best way to get something that was spec compliant and still behaved in a useful way when responding to a browser (the spec deliberately avoids talking about that case explicitly).
No, it's not currently possible. I intentionally suppressed the parameter handling option in the ContentNegotiationManagerFactoryBean because the spec didn't have anything like that in it.
It would be possible in principle to enable that mechanism and map something like ?format=raw to be equivalent to asking for application/samlmetadata+xml, but I'm not sure that's really what your SP user wants. The SP itself will always query with an appropriate Accept header, and if he wants to pull it manually it's a lot safer to use curl or wget than it is trusting a browser to save the file properly without breaking it in some way.
Hope that helps,
- Re: [Metadata-Support] MDQ format options?, (continued)
- Re: [Metadata-Support] MDQ format options?, Klingenstein, Nate, 12/07/2016
- Re: [Metadata-Support] MDQ format options?, Cantor, Scott, 12/07/2016
Archive powered by MHonArc 2.6.19.