Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Backport of Use a less strict URL validation for PKI issuing and crl distribution urls into release/1.16.x #26512

Conversation

hc-github-team-secure-vault-core
Copy link
Collaborator

Backport

This PR is auto-generated from #26477 to be assessed for backporting due to the inclusion of the label backport/1.16.x.

The below text is copied from the body of the original PR.


The library we were using is quite strict about what is and is not a URL, in
order to catch errors. But its strictness prevents unanticipated uses
schems unknown to it, for example, ldap:

Use Go's URL parser instead.


Overview of commits

@hc-github-team-secure-vault-core hc-github-team-secure-vault-core force-pushed the backport/sgm/looser-url-parsing/moderately-relevant-filly branch from f381f47 to 4b080ff Compare April 18, 2024 17:35
@github-actions github-actions bot added the hashicorp-contributed-pr If the PR is HashiCorp (i.e. not-community) contributed label Apr 18, 2024
Copy link

github-actions bot commented Apr 18, 2024

CI Results:
All Go tests succeeded! ✅

@sgmiller sgmiller enabled auto-merge (squash) April 18, 2024 17:44
@sgmiller sgmiller added this to the 1.16.2 milestone Apr 18, 2024
Copy link

Build Results:
All builds succeeded! ✅

…m/looser-url-parsing/moderately-relevant-filly
@sgmiller sgmiller merged commit 8645e74 into release/1.16.x Apr 18, 2024
76 checks passed
@sgmiller sgmiller deleted the backport/sgm/looser-url-parsing/moderately-relevant-filly branch April 18, 2024 18:22
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
hashicorp-contributed-pr If the PR is HashiCorp (i.e. not-community) contributed
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants