Shibboleth Developers

[c wilper <>]

Coneg sounds to me to be the most appropriate, (vs.
USER_AGENT or even ?xml=true).

On another note...  I just had a good meeting with
another Fedora developer about this non-html-client
stuff and parsing, following redirects, etc..  Around
Q1 we will probably be interested in collaborating
with anyone else in a similar situation... to write a
java client library that takes care of this stuff,
senses whether the Target has redirected to a WAYF or
a HS, etc.

- Chris

--- Scott Cantor 
<>
 wrote:
> > Is it recommended that a non-html client parse the
> > xhtml's option elements (much in the same way it
> would
> > have to parse the xhtml form with the
> base-64-encoded
> > xml samlresponse from the HS).... or would direct
> > access to the WAYF's sites.xml file be provided at
> > some point?
> 
> Direct access to the file is not a problem (it
> already is public), but the
> trick is that your web interface doesn't distinguish
> between your browser
> users and your Java client, and doesn't know to do
> anything different.
> 
> I would think the optimum solution in the short term
> is to tweak the WAYF to
> sniff for a user agent or other HTTP header to
> signal to it that the
> presentation to the client should be XML. Perhaps
> just content negotiation
> via the Accept header, even.
> 
> -- Scott
> 
>
> 


__________________________________
Do you Yahoo!?
The New Yahoo! Shopping - with improved product search
http://shopping.yahoo.com

------------------------------------------------------mace-shib-design-+
For list utilities, archives, subscribe, unsubscribe, etc. please visit the
ListProc web interface at 

    http://archives.internet2.edu/

------------------------------------------------------mace-shib-design--