12dcc60 Don't allow CDN's to send cached responses
📊 Changes
1 file changed (+3 additions, -3 deletions)
View changed files
📝dehydrated (+3 -3)
📄 Description
A lot of CA's use a CDN service to protect and speed up their ACME service. These CDN services can sometimes miss-behave and send cached results. For example DigiCert's ACME service uses the Imperva CDN. It will send cached results on the DNS validation, challenge endpoint, resulting in it being stuck in the processing status, thus dehydrated is hung and never gets the certificate.
🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.
## 📋 Pull Request Information
**Original PR:** https://github.com/dehydrated-io/dehydrated/pull/972
**Author:** [@GTAXL](https://github.com/GTAXL)
**Created:** 6/1/2025
**Status:** ❌ Closed
**Base:** `master` ← **Head:** `master`
---
### 📝 Commits (1)
- [`12dcc60`](https://github.com/dehydrated-io/dehydrated/commit/12dcc60ce102e5ee65949b91852d14bfbffd57a7) Don't allow CDN's to send cached responses
### 📊 Changes
**1 file changed** (+3 additions, -3 deletions)
<details>
<summary>View changed files</summary>
📝 `dehydrated` (+3 -3)
</details>
### 📄 Description
A lot of CA's use a CDN service to protect and speed up their ACME service. These CDN services can sometimes miss-behave and send cached results. For example DigiCert's ACME service uses the Imperva CDN. It will send cached results on the DNS validation, challenge endpoint, resulting in it being stuck in the processing status, thus dehydrated is hung and never gets the certificate.
---
<sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
📋 Pull Request Information
Original PR: https://github.com/dehydrated-io/dehydrated/pull/972
Author: @GTAXL
Created: 6/1/2025
Status: ❌ Closed
Base:
master← Head:master📝 Commits (1)
12dcc60Don't allow CDN's to send cached responses📊 Changes
1 file changed (+3 additions, -3 deletions)
View changed files
📝
dehydrated(+3 -3)📄 Description
A lot of CA's use a CDN service to protect and speed up their ACME service. These CDN services can sometimes miss-behave and send cached results. For example DigiCert's ACME service uses the Imperva CDN. It will send cached results on the DNS validation, challenge endpoint, resulting in it being stuck in the processing status, thus dehydrated is hung and never gets the certificate.
🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.