Per-Entity Metadata Working Group

[Tom Mitchell <>]

Whoops, and apologies. You used the fake URLs I sent previously, so you were 
looking at responses from someone else’s server. As I mentioned previously, 
those were fake URLs. The URL below has also been cleaned for the mail server 
logs.

Using “ForceType”, I think I’m getting close. It’s got the right content type 
and has the ETag header, which I assume is what you were looking for.

$ curl --silent --dump-header /dev/tty 
http://example.com/entities/%7Bsha1%7Dd4d1ca999a5a9352fa618075eac456eb67956c74
 > /dev/null
HTTP/1.1 200 OK
Date: Thu, 28 Jul 2016 20:12:42 GMT
Server: Apache/2.4.6 (CentOS)
Last-Modified: Thu, 28 Jul 2016 19:58:57 GMT
ETag: "258b-538b7907b51cf"
Accept-Ranges: bytes
Content-Length: 9611
Content-Type: application/samlmetadata+xml


What else is this missing? And thanks very much for the fast feedback.

Tom


> On Jul 28, 2016, at 3:24 PM, Tom Scavo 
> <>
>  wrote:
> 
> Oh, and another thing is HTTP Conditional GET. In any case, here are
> two requests for comparison:
> 
> $ curl --silent --dump-header /dev/tty
> http://myserver.org/entities/urn%3Amace%3Aincommon%3Aosu.edu >
> /dev/null
> HTTP/1.1 301 Moved Permanently
> Date: Thu, 28 Jul 2016 19:11:34 GMT
> Server: Microsoft-IIS/6.0
> Pragma: no-cache
> Cache-Control: no-cache
> Content-Type: text/html
> Content-Length: 227
> Location: http://www.MyServer.org/entities/urn%3Amace%3Aincommon%3Aosu.edu
> 
> $ curl --silent --dump-header /dev/tty
> http://mdq-beta.incommon.org/global/entities/urn%3Amace%3Aincommon%3Aosu.edu
>> /dev/null
> HTTP/1.1 200 OK
> Date: Thu, 28 Jul 2016 19:23:38 GMT
> X-Application-Context: application:sign:80
> Content-Language: en
> Content-Type: application/samlmetadata+xml; charset=UTF-8
> ETag: "8b2f4313e9747e618af5a790fa3a7bdf4e2eaf57"
> Content-Length: 9611
> Server: Jetty(9.2.15.v20160210)
> 
> 
> On Thu, Jul 28, 2016 at 3:18 PM, Tom Scavo 
> <>
>  wrote:
>> On Thu, Jul 28, 2016 at 2:46 PM, Tom Mitchell 
>> <>
>>  wrote:
>>> 
>>> The first URL is from the spec, and serves up some text. The other two 
>>> will
>>> serve up the real data grabbed from the MDQ beta server. I think they
>>> represent the two main kinds of entity IDs in InCommon and eduGAIN. Let me
>>> know if I should try others.
>> 
>> This is good progress, Tom, but you've saved the most difficult parts
>> to last :-)
>> 
>> Click this link in your browser:
>> http://mdq-beta.incommon.org/global/entities/urn%3Amace%3Aincommon%3Aosu.edu
>> 
>> Note that there are two IDs that return the same metadata:
>> 
>> urn:mace:incommon:osu.edu
>> {sha1}d4d1ca999a5a9352fa618075eac456eb67956c74
>> 
>> The MDQ server needs to support both.
>> 
>> As a small thing, the content-type is wrong. It should be
>> 
>> Content-Type: application/samlmetadata+xml
>> 
>> not
>> 
>> Content-Type: text/html
>> 
>> 
>> Tom