NodeJS - Superagent. SSL23_GET_SERVER_HELLO when try GET method over HTTPS
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty height:90px;width:728px;box-sizing:border-box;
Following the documentation of an API Service, I have found out that I have to make request to the following URL
https://eipapp1.emeter.com:9674
I am using superagent module of Node.JS. And I am getting the following error:
Error: write EPROTO 140736110642048:error:140770FC:SSL routines:SSL23_GET_SERVER_HELLO:unknown protocol:../deps/openssl/openssl/ssl/s23_clnt.c:825:
I understand that this error is because I am making a Request to the 9674 port but using HTTPS, and thats could be the reason.
There exists a way to make this kind of request? Could be a problem with the API Service specification?
Thanks to all.
node.js ssl https request superagent
asked Nov 15 '18 at 15:57
Luis GonzálezLuis González
2,0021131
add a comment |
Following the documentation of an API Service, I have found out that I have to make request to the following URL
https://eipapp1.emeter.com:9674
I am using superagent module of Node.JS. And I am getting the following error:
Error: write EPROTO 140736110642048:error:140770FC:SSL routines:SSL23_GET_SERVER_HELLO:unknown protocol:../deps/openssl/openssl/ssl/s23_clnt.c:825:
I understand that this error is because I am making a Request to the 9674 port but using HTTPS, and thats could be the reason.
There exists a way to make this kind of request? Could be a problem with the API Service specification?
Thanks to all.
node.js ssl https request superagent
asked Nov 15 '18 at 15:57
Luis GonzálezLuis González
2,0021131
It is very likely that the URL you are trying to access does not support https at all. This kind of error message is typical for cases where one tries to connect to a host:port by https even though only http (or other non-TLS protocols) is supported. Unfortunately, the site is not public so I cannot verify this.
– Steffen Ullrich
Nov 15 '18 at 16:55
"because I am making a Request to the 9674 port but using HTTPS, and thats could be the reason. ". No. Typically HTTPS uses port 443 because it has been defined like that by IANA and because the web world does not useSRVrecords to differentiate the service identification from the service location, so a fixed default port is needed. But you can do HTTP or HTTPS over any other port, that works exactly in the same way, if client and server agree. HTTP is (at least for now) layered over TCP (or over TLS layered itself over TCP) and addresses/ports are TCP-level problems, not HTTP(s) ones.
– Patrick Mevzek
Nov 15 '18 at 19:47
add a comment |
Following the documentation of an API Service, I have found out that I have to make request to the following URL
https://eipapp1.emeter.com:9674
I am using superagent module of Node.JS. And I am getting the following error:
Error: write EPROTO 140736110642048:error:140770FC:SSL routines:SSL23_GET_SERVER_HELLO:unknown protocol:../deps/openssl/openssl/ssl/s23_clnt.c:825:
I understand that this error is because I am making a Request to the 9674 port but using HTTPS, and thats could be the reason.
There exists a way to make this kind of request? Could be a problem with the API Service specification?
Thanks to all.
node.js ssl https request superagent
asked Nov 15 '18 at 15:57
Luis GonzálezLuis González
2,0021131
Following the documentation of an API Service, I have found out that I have to make request to the following URL
https://eipapp1.emeter.com:9674
I am using superagent module of Node.JS. And I am getting the following error:
Error: write EPROTO 140736110642048:error:140770FC:SSL routines:SSL23_GET_SERVER_HELLO:unknown protocol:../deps/openssl/openssl/ssl/s23_clnt.c:825:
I understand that this error is because I am making a Request to the 9674 port but using HTTPS, and thats could be the reason.
There exists a way to make this kind of request? Could be a problem with the API Service specification?
Thanks to all.
node.js ssl https request superagent
node.js ssl https request superagent
asked Nov 15 '18 at 15:57
Luis GonzálezLuis González
2,0021131
asked Nov 15 '18 at 15:57
Luis GonzálezLuis González
2,0021131
edited Nov 16 '18 at 10:02
Luis González
asked Nov 15 '18 at 15:57
Luis GonzálezLuis González
2,0021131
asked Nov 15 '18 at 15:57
Luis GonzálezLuis González
2,0021131
asked Nov 15 '18 at 15:57
Luis GonzálezLuis González
2,0021131
2,0021131
It is very likely that the URL you are trying to access does not support https at all. This kind of error message is typical for cases where one tries to connect to a host:port by https even though only http (or other non-TLS protocols) is supported. Unfortunately, the site is not public so I cannot verify this.
– Steffen Ullrich
Nov 15 '18 at 16:55
"because I am making a Request to the 9674 port but using HTTPS, and thats could be the reason. ". No. Typically HTTPS uses port 443 because it has been defined like that by IANA and because the web world does not useSRVrecords to differentiate the service identification from the service location, so a fixed default port is needed. But you can do HTTP or HTTPS over any other port, that works exactly in the same way, if client and server agree. HTTP is (at least for now) layered over TCP (or over TLS layered itself over TCP) and addresses/ports are TCP-level problems, not HTTP(s) ones.
– Patrick Mevzek
Nov 15 '18 at 19:47
add a comment |
It is very likely that the URL you are trying to access does not support https at all. This kind of error message is typical for cases where one tries to connect to a host:port by https even though only http (or other non-TLS protocols) is supported. Unfortunately, the site is not public so I cannot verify this.
– Steffen Ullrich
Nov 15 '18 at 16:55
"because I am making a Request to the 9674 port but using HTTPS, and thats could be the reason. ". No. Typically HTTPS uses port 443 because it has been defined like that by IANA and because the web world does not useSRVrecords to differentiate the service identification from the service location, so a fixed default port is needed. But you can do HTTP or HTTPS over any other port, that works exactly in the same way, if client and server agree. HTTP is (at least for now) layered over TCP (or over TLS layered itself over TCP) and addresses/ports are TCP-level problems, not HTTP(s) ones.
– Patrick Mevzek
Nov 15 '18 at 19:47
It is very likely that the URL you are trying to access does not support https at all. This kind of error message is typical for cases where one tries to connect to a host:port by https even though only http (or other non-TLS protocols) is supported. Unfortunately, the site is not public so I cannot verify this.
– Steffen Ullrich
Nov 15 '18 at 16:55
It is very likely that the URL you are trying to access does not support https at all. This kind of error message is typical for cases where one tries to connect to a host:port by https even though only http (or other non-TLS protocols) is supported. Unfortunately, the site is not public so I cannot verify this.
– Steffen Ullrich
Nov 15 '18 at 16:55
"because I am making a Request to the 9674 port but using HTTPS, and thats could be the reason. ". No. Typically HTTPS uses port 443 because it has been defined like that by IANA and because the web world does not use
SRV records to differentiate the service identification from the service location, so a fixed default port is needed. But you can do HTTP or HTTPS over any other port, that works exactly in the same way, if client and server agree. HTTP is (at least for now) layered over TCP (or over TLS layered itself over TCP) and addresses/ports are TCP-level problems, not HTTP(s) ones.– Patrick Mevzek
Nov 15 '18 at 19:47
"because I am making a Request to the 9674 port but using HTTPS, and thats could be the reason. ". No. Typically HTTPS uses port 443 because it has been defined like that by IANA and because the web world does not use
SRV records to differentiate the service identification from the service location, so a fixed default port is needed. But you can do HTTP or HTTPS over any other port, that works exactly in the same way, if client and server agree. HTTP is (at least for now) layered over TCP (or over TLS layered itself over TCP) and addresses/ports are TCP-level problems, not HTTP(s) ones.– Patrick Mevzek
Nov 15 '18 at 19:47
add a comment |
0
active
oldest
votes
Your Answer
StackExchange.ifUsing("editor", function ()
StackExchange.using("externalEditor", function ()
StackExchange.using("snippets", function ()
StackExchange.snippets.init();
);
);
, "code-snippets");
StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "1"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);
else
createEditor();
);
function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);
);
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53323272%2fnodejs-superagent-ssl23-get-server-hello-when-try-get-method-over-https%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
0
active
oldest
votes
0
active
oldest
votes
active
oldest
votes
active
oldest
votes
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53323272%2fnodejs-superagent-ssl23-get-server-hello-when-try-get-method-over-https%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
It is very likely that the URL you are trying to access does not support https at all. This kind of error message is typical for cases where one tries to connect to a host:port by https even though only http (or other non-TLS protocols) is supported. Unfortunately, the site is not public so I cannot verify this.
– Steffen Ullrich
Nov 15 '18 at 16:55
"because I am making a Request to the 9674 port but using HTTPS, and thats could be the reason. ". No. Typically HTTPS uses port 443 because it has been defined like that by IANA and because the web world does not use
SRVrecords to differentiate the service identification from the service location, so a fixed default port is needed. But you can do HTTP or HTTPS over any other port, that works exactly in the same way, if client and server agree. HTTP is (at least for now) layered over TCP (or over TLS layered itself over TCP) and addresses/ports are TCP-level problems, not HTTP(s) ones.– Patrick Mevzek
Nov 15 '18 at 19:47