QA

As defined in the base specification, a metadata query request URL is constructed by concatenating the following four components (two of which are variable):

1. The Metadata Query Server's base URL
2. A single "/" character, unless the base URL already ends in a "/"
3. The string "entities/"
4. A single URL-encoded entityID

For example, if the base URL is http://mdq.example.com/public and the entityID is https://sso.example.org/idp, the request URL is - 
    http://yourlocalservername/entities/https%3A%2F%2Fsso.example.org%2Fidp

OR

    http://yourlocalservername/api/entities/https%3A%2F%2Fsso.example.org%2Fidp

Therefore - a GET to the correct URL (ie for an existing entity id) should return the entity definition with the headers:

MUST:

• Content-Encoding (only if compressed - which the response shouldn't be, so this may or may not be here)
• Content-Type
• ETag

SHOULD:

• Cache-Control
• Content-Length
• Last-Modified