Hi there, we have noticed that on Staging, after recent changes that enable Asynchronous Order Finalization ( Enabling Asynchronous Order Finalization ) our client stopped working, because /order endpoint no longer returns in Location itself. Example: New API: finalize: https://acme-staging-v02.a…

@lestaff is this change intended?

Hi there, thanks for the report! This exactly the kind of bug that staging deployments are meant to uncover. I don't expect the change to have affected the Location header but I'll look into it today.

It's worth noting that RFC 8555 does not require a Location header for Finalize and Poll Order requests, only for New Order requests: The following table illustrates a typical sequence of requests required to establish a new account with the server, prove control of an identifier, issue a …

[image] aarongable: I'm happy to update our code to return a Location header in our get-order responses, but you should definitely update your client to work with servers that do not do so. The client should also have a test suite that runs against the Pebble server, which implements the RFC …

Thanks for investigation. We already updated code to not rely on the Location, so future versions of our product should be fully compatible with upcoming API. But if possible we would love to maintain backward compatibility due to older software versions that are already deployed by our customers, s…

Thanks for the tip, we will definitely set it up.

Can you PM me the user agent used by your client please? I'd like to do some spelunking through our logs.

[image] Plesk: Certificate location not specified in response Issuance Tech P… looks like plesk not like this change

I do think that error is related to async finalize, but I don't think it's related to Location headers. We'll keep that discussion over there.

[image] Enabling Asynchronous Order Finalization API Announcements T… We've disabled the brownout early because of problems like this

Breaking changes in Asynchronous Order Finalization API

Client dev

mcpherrinm April 5, 2023, 10:45pm 11

We've disabled the brownout early because of problems like this

Topic		Replies	Views
Enabling Asynchronous Order Finalization API Announcements	7	5852	April 6, 2023
Client access delay for asynchronous order finalization Client dev	1	533	May 6, 2023
myVesta / HestiaCP / VestaCP: fail issuance with async finalization Client dev	11	1399	May 6, 2023
Is the "Location" header of an new order the order's url in Boulder/LetsEncrypt? Client dev	8	1423	March 12, 2020
Plesk: Certificate location not specified in response Issuance Tech	15	1596	May 6, 2023

Breaking changes in Asynchronous Order Finalization API

Related topics