-
Notifications
You must be signed in to change notification settings - Fork 325
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
HTTPS API endpoint is downgraded to HTTP #652
Labels
kind/bug
A bug in existing code (including security flaws)
Comments
I think, perhaps, this is the cause...? (Look closely at the spelling of Here's the dump of the config object I managed to retrieve from the parameter of {
"api-path":"/api/v0/",
"user-agent":"/node-ipfs-api/26.1.2/",
"host":"[redacted]",
"port":"",
"protocol":"http",
"procotol":"https:"
} |
yvt
changed the title
Can't use a HTTPS API endpoint
HTTPS API endpoint is downgraded to HTTP
Jan 7, 2019
@yvt wow that is a sneaky typo, great catch! |
yvt
added a commit
to yvt/ipfs-companion
that referenced
this issue
Jan 8, 2019
This commit fixes the issue that a protocol name (http or https) is not passed to `ipfs-http-client` as intended. Closes ipfs#652
lidel
pushed a commit
that referenced
this issue
Jan 8, 2019
This commit fixes the issue that a protocol name (http or https) is not passed to `ipfs-http-client` as intended. Closes #652
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The protocol part of the endpoint URL is always ignored and assumed to be
http
.For example, if you specify
https://www.example.com
, all requests are actually sent tohttp://www.example.com
. Although this usage scenario is very uncommon, this can unintentionally open possibilities for information leakage and MITM attacks.The text was updated successfully, but these errors were encountered: