Subject: [apps-discuss] draft-nottingham-http-problem in practice at Akamai

From: "Stevens, Matt" <[email-masked]>
Date: Mon, 4 Aug 2014 10:26:41 -0400

regarding ³Call for Adoption² posting

https://mailarchive.ietf.org/arch/msg/apps-discuss/2AI4dwxLgScBGax1n8mBBJ0q
dm4

Akamai Technologies has adopted HTTP Problem specification internally and
externally as a convention in our Platform web resource representations as
published at

https://developer.akamai.com/

We had previously issued error representations as application/json and are
transitioning to application/problem+json

For example:

https://some-service-consumer.luna.akamaiapis.net/some-endpoint/some-resour
ce

HTTP/1.1 400 Bad Request
Content-Length: 395
Date: Mon, 04 Aug 2014 14:07:40 GMT
Connection: close
Content-Type: application/problem+json

{
  "type": "https://problems.luna.akamaiapis.net/-/pep-authn/request-error",
  "title": "Bad request",
  "status": 400,
  "detail": "Invalid endpoint",
  "instance": 
"https://some-service-consumer.luna.akamaiapis.net/some-endpoint/some-resou
rce",
  "method": "GET",
  "serverIp": "72.246.153.146",
  "clientIp": "80.67.64.116",
  "requestId": ³123",
  "requestTime": "2014-08-04T14:07:40Z"
}

We have been using HTTP Problem in practice for a year externally and
since early 2013 internally.

regards,
Matt Stevens
Akamai Technologies