Open weierophinney opened 4 years ago
:+1:
Originally posted by @michalkopacz at https://github.com/zfcampus/zf-api-problem/issues/26#issuecomment-63623826
Via http://tools.ietf.org/html/draft-nottingham-http-problem-07#section-4
Problem details are not a debugging tool for the underlying implementation; rather, they are a way to expose greater detail about the HTTP interface itself.
Originally posted by @snapshotpl at https://github.com/zfcampus/zf-api-problem/issues/26#issuecomment-69750265
API Problem response with HTTP status code from exception when it's valid rage of HTTP codes. But what about situation when some library throws own exceptions, with own codes (example 302, and it means that user doesn't exist)? It does't make sense. My solution for this is to use code from exceptions only when exception implements
\ZF\ApiProblem\Exception\ExceptionInterface
Originally posted by @snapshotpl at https://github.com/zfcampus/zf-api-problem/issues/26