Acme HTTP Errors

[barryvdh]

Acme HTTP Errors

[kelunik]

BadCsrException, BadNonceException, ConnectException, DnssecException, MalformedRequestException, InternalServerException, TlsException, UnauthorizedException, UnknownHostException.

I'm not happy with some of these names, do you have suggestions?

[kelunik]

Another alternative would be to return the type in AcmeException::getCode.

[staabm]

I agree that all of those errors should be represented by 1 class (not 1 each) which then provides a method to further determine the underlying error

[kelunik]

I have improved the error messages, please review d3805a6.

[barryvdh]

What about doing the type/detail handling inside the exception?

You can change the Exception constructor when extending, for example to typehint a Response object. You can then apply the same logic in your Eception.
You could also create a static factory for your AcmeException, to create on from a Response.

class AcmeException extends Exception {
    public function __construct($message, Response $response = null, Exception $previous = null)
    {
        parent::__construct($message, 0, $previous);

        if ($response) {
            $info = json_decode($response->getBody(), true);

            if ($info && isset($info['type'], $info['detail'])) {
                $this->code = $info['type'];
                $this->message .= ' ' . $info['detail'];
            }
        }

    }
}

https://3v4l.org/WgOnF

[kelunik]

Should the default error code be internal, generic, general or unknown?

[barryvdh]

Don't know, could just leave it 0, the Exception default.

[kelunik]

Can I close this?

[barryvdh]

Hmm, using a string as code might give unexpected results when stacking exceptions, see: zenire/da-letsencrypt#40
Testcase: https://3v4l.org/ObN47