Client and Server Implementation Guidelines for Common HTTP Use cases

[kkostov]

When creating a production implementation of the spec (both client and server-side), it may be beneficial to have access to a set of guidelines on how to tackle common technical implementation details:

• Handling of redirects along the graph
• Handling upgrade of HTTP to HTTPS
• CORS
• The need to pass custom headers in case of scenarios like authentication or API limits?
• ...

[pietercolpaert]

Found an interesting example for this: https://iiif.io/api/discovery/1.0/#4-network-considerations

[kkostov]

@pietercolpaert this is an excellent example, I like that the guidelines also appear as a SHOULD.

[sandervd]

• A server should define a default Accept header (e.g. if no accept is defined, return content type Turtle)