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

Jump to bottom

crypto/tls: be more specific about errors bad record MAC #51837

Open
OO00O0O opened this issue Mar 21, 2022 · 1 comment
Open

crypto/tls: be more specific about errors bad record MAC #51837

OO00O0O opened this issue Mar 21, 2022 · 1 comment
Labels
NeedsInvestigation Someone must examine and confirm this is a valid issue and not a duplicate of an existing one.
Milestone
Unplanned

Comments

@OO00O0O
Copy link

OO00O0O commented Mar 21, 2022 •
edited

I've got error tls: bad record MAC
Problem was that service was making request over https://127.0.0.1, rather http://127.0.0.1.
Proposal would be, to provide more specific error message that could be used resolving incidents.
Example: bad record MAC - request without domain
@gopherbot gopherbot added this to the Proposal milestone Mar 21, 2022
@seankhliao seankhliao changed the title proposal: Be more specific about errors bad record MAC affected/package: TLS crypto/tls: be more specific about errors bad record MAC Mar 21, 2022
@seankhliao seankhliao added NeedsInvestigation Someone must examine and confirm this is a valid issue and not a duplicate of an existing one. and removed Proposal labels Mar 21, 2022
@seankhliao seankhliao removed this from the Proposal milestone Mar 21, 2022
@seankhliao
Copy link
Member

cc @FiloSottile

@seankhliao seankhliao added this to the Unplanned milestone Aug 20, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
NeedsInvestigation Someone must examine and confirm this is a valid issue and not a duplicate of an existing one.
Projects
None yet
Milestone
Unplanned
Development

No branches or pull requests
3 participants
@OO00O0O @gopherbot @seankhliao