Open TinaHeiligers opened 1 week ago
Thanks, I can recreate the problem too. I will follow up with Bump.sh
Hi @lcawl,
We use a POST request for this action on the docs @bump.sh, I believe that ~your proxy is blocking POST
requests~ your proxy doesn't seem to send the necessary X-Forwarded-Host
header. Could you check if that's something that can be adapted on your side?
Let me know if you have any questions!
EDIT: I've checked in our logs and can see there's a mismatch origin host which makes us respond with a 422 error, so the proxy sends the POST request correctly to our servers but it seems to lack some necessary headers so we can't verify the original host
header sent by the client. Notably, we would need the proxy to add those headers:
X-Forwarded-Proto 'https'
X-Forwarded-Port 433
X-Forwarded-Host 'https://www.elastic.co'
Was the documentation helpful?
Yes
What documentation page is affected
https://www.elastic.co/docs/api/doc/serverless/compare/79ff5f69-7a76-436d-b09d-de5cfe42eb77 Similarly, for previous release dates: https://www.elastic.co/docs/api/doc/serverless/compare/1853d895-f245-46a4-b2a8-e51e589746af
Description
Selecting a version responds with 422.