Have less strict content type checking
Closed this issue · 2 comments
Right now, txacme has a very strict check for content type headers and you end up with errors like
Unexpected response Content-Type: 'application/json; charset=utf-8'
I am getting that error with pebble.
I will soon create a public pebble server and we can start writing tests not only against Boulder staging, but also against pebble.
And then I will fix the code :)
....... I am still trying to see how to set up pebble the right way, as even after I fix the content type, it fails to get a certificate due to missing fields in the response body... I might not run the right version of pebble
ok. It looks like pebble is v2 only (or more precisely latest ACME) letsencrypt/pebble#58 (comment)
since txacme is v1 only, we can't just yet use pebble for testing.
but I think that we can still fix the content-type matching code to prepare for the future