RFC7030 mandates response code 200 and HTTP content-type of "application/pkcs7-mime" with an smime-type parameter "certs-only".
(so it's Content-Type: application/pkcs7-mime; smime-type=certs-only )
But this server send 201 response code and skips smime-type parameter from content-type
https://datatracker.ietf.org/doc/html/rfc7030#section-4.4.3
Because of this any correct EST client will reject enroll/reenroll response from this server, but it's kinda hard to change now though because fioconfig have same wrong interpretation of rfc7030 requirement, making this breaking change, but it should at least documented.
https://github.com/foundriesio/fioconfig/blob/87efd8b30ea163b2bc97d9ed43c3a666f29864f8/internal/rotate_est.go#L85
RFC7030 mandates response code 200 and HTTP content-type of "application/pkcs7-mime" with an smime-type parameter "certs-only".
(so it's Content-Type: application/pkcs7-mime; smime-type=certs-only )
But this server send 201 response code and skips smime-type parameter from content-type
https://datatracker.ietf.org/doc/html/rfc7030#section-4.4.3
Because of this any correct EST client will reject enroll/reenroll response from this server, but it's kinda hard to change now though because fioconfig have same wrong interpretation of rfc7030 requirement, making this breaking change, but it should at least documented.
https://github.com/foundriesio/fioconfig/blob/87efd8b30ea163b2bc97d9ed43c3a666f29864f8/internal/rotate_est.go#L85