Nodejs Error: Protocol "http:" not supported. Expected "https:"

Question

I am using request module for node.js and time by time i'm getting uncaught error (only on production, maybe after node.js updating)

Node version: 0.12.4, request version: 2.55.0

1000-2000 requests can be executed successfully, but then i'm getting such error:

Error: Protocol "http:" not supported. Expected "https:".
    at new ClientRequest (_http_client.js:75:11)
    at Object.exports.request (http.js:49:10)
    at Request.start (/path/node_modules/request/request.js:963:30)
    at Request.end (/path/node_modules/request/request.js:1531:10)
    at end (/path/node_modules/request/request.js:734:14)
    at Immediate._onImmediate (/path/node_modules/request/request.js:748:7)
    at processImmediate [as _immediateCallback] (timers.js:358:17)"

How can i fix it? Why it appears? Thanks)

Are you using socks5-https-client with Request? github.com/mattcg/socks5-https-client/issues/6 — chedabob
– chedabob, Commented May 28, 2015 at 10:40

Nick Duncan · Accepted Answer · 2017-09-13 05:58:10Z

8

This is caused by running your application using SSL but calling it via normal HTTP. You would need to put a check in place to identify if the client is using HTTP or HTTPS and then modify your code to suit.

Something like this should work:

var express = require('express')
    , http = require('http')
    , https = require('https')
    , app = express();

http.createServer(app);
https.createServer({ ... }, app);

Then when you handle your request, do something like

app.get('/your-route', function(req, res) {
    if (req.secure) {
        var req = https.get(url, function(res) { ... });
    } else {
        var req = http.get(url, function(res) { ... });
    }
});

req.secure identifies if the connection is secure. Notice how we use https and http depending on the connection type.

answered Sep 13, 2017 at 5:58

Nick Duncan

8296 silver badges17 bronze badges

Sign up to request clarification or add additional context in comments.

Comments

Vincent · Accepted Answer · 2020-08-30 20:41:39Z

3

just FYI, I got a similar error

TypeError [ERR_INVALID_PROTOCOL]: Protocol "http:" not supported. Expected "https:"
    at new ClientRequest (_http_client.js:120:11)
    at request (http.js:42:10)
    at ..../node_modules/node-fetch/lib/index.js:1432:15
    at new Promise (<anonymous>)
    at fetch (..../node_modules/node-fetch/lib/index.js:1401:9)
    at ClientRequest.<anonymous> (..../node_modules/node-fetch/lib/index.js:1532:15)
    at ClientRequest.emit (events.js:198:13)
    at HTTPParser.parserOnIncomingClient [as onIncoming] (_http_client.js:565:21)
    at HTTPParser.parserOnHeadersComplete (_http_common.js:111:17)
    at TLSSocket.socketOnData (_http_client.js:451:20)
    at TLSSocket.emit (events.js:198:13)
    at addChunk (_stream_readable.js:288:12)
    at readableAddChunk (_stream_readable.js:269:11)
    at TLSSocket.Readable.push (_stream_readable.js:224:10)
    at TLSWrap.onStreamRead (internal/stream_base_commons.js:94:17)

which was due to a dumb typo in the url in the fetch instruction

        fetch(`https://[email protected]`, {
            method: 'post',
            body: JSON.stringify(eventLogEntry),
            headers: { 'Content-Type': 'application/json' },
            agent: agent
        })

my problem went away when I fixed the url to xxx.yyy.com

answered Aug 30, 2020 at 20:41

Vincent

812 bronze badges

1 Comment

Sergey Pleshakov Over a year ago

I bet I would have spent days on this if not your answer

Collectives™ on Stack Overflow

Nodejs Error: Protocol "http:" not supported. Expected "https:"

2 Answers 2

Comments

1 Comment

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

2 Answers 2

Comments

1 Comment

Your Answer

Sign up or log in

Post as a guest

Related