Handle SSL certificate verifications for others than Let's Encrypt #31856
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Do no longer (wrongly) rewrite URLs like
for automated SSL certificate verifications. All (common commercial) certificate authorities (CA) except Let's Encrypt (via ACME) seem to use "pki-validation" rather "acme-challenge" for their domain control validation (DCV). Note that this is required inside of ownCloud rather on web server level due to shared web hosting systems, where the customer/user might not be able to do this on web server level (Apache/Nginx configuration changes for the virtual host).
As per https://owncloud.org/community/develop/contributor-agreement/ I am releasing my code/contribution (this PR) under the MIT license.