<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<br>
<div class="moz-cite-prefix">On 11/8/13 3:02 PM, Brent Putman wrote:<br>
</div>
<blockquote cite="mid:527D433D.9060002@georgetown.edu" type="cite">
<pre wrap="">
So it's handing back the literal response body "Sorry, we cannot support
your client.".
So, their web server is at fault. They must be doing some kind of
validation on some aspect of the request (e.g. User-Agent header), and
therefore refusing to service requests coming from the IdP's HTTP
metadata provider.</pre>
</blockquote>
<br>
FYI, I did a little additional debugging since I really wanted to
know what was going on here. It's definitely the User-Agent
header. I reproduced this using our v3 stack and Apache HttpClient
4.3.1, which is easier to work with and get useful debug output out
of.<br>
<br>
Basically they're rejecting the client's default User-Agent of:
Apache-HttpClient/4.3.1 (java 1.5)<br>
<br>
You can even reproduce this with curl:<br>
<br>
curl -v --user-agent "Apache-HttpClient/4.3.1 (java 1.5)"
<a class="moz-txt-link-freetext" href="http://myreviewroom.com/saml2/metadata/">http://myreviewroom.com/saml2/metadata/</a><br>
<br>
It also rejects just the simpler form "Apache-HttpClient". Removing
the hypen ("ApacheHttpClient") does make it work, so at first I
thought maybe the server is just broken around hyphens in the header
value. But other random user agent strings with hyphens seem to
work ok, e.g. "Brent-HttpClient". However,
"Brent-Apache-HttpClient" does not. So maybe the server is matching
on a regex like "Apache-" or something, I don't know.<br>
<br>
According to the Server header, their server is apparently Cherokee
1.2.101, running on Ubuntu, of which I have zero knowledge or
experience. Tried googling for hints, but didn't find anything yet.<br>
<br>
If you contact them and they figure it out, I'd be interested in
hearing what the issue and resolution was. We make heavy use of
Apache HttpClient for various HTTP-related components, and so this
might come up again in the future if this is a general Cherokee web
server issue, as opposed to some local configuration choice.<br>
<br>
Thanks,<br>
Brent<br>
<br>
<br>
</body>
</html>