Node-http-proxy: Getting a lot of ERR_CONTENT_LENGTH_MISMATCH errors for HTTPS

Created on 16 Apr 2014 · 13Comments · Source: http-party/node-http-proxy

When proxying HTTPS to HTTP, I am getting a lot of ERR_CONTENT_LENGTH_MISMATCH errors in Chrome. For example, if I request an image from the web server through the HTTPS proxy, I get a content length of 50KB but the downloaded image is 30KB (and the image appears to be half-downloaded). This is true for _any_ HTTPS request, not just images. This is also true for _any_ web browser. I am testing in a Windows environment with a fairly slow Internet connection.

Perhaps the connection is ending prematurely? Any thoughts on this?

Source

bminer

Most helpful comment

Using globalAgent seems to solve this issue for me :

var http = require('http');
var httpProxy = require('http-proxy');

var proxy = httpProxy.createProxyServer({
    target : "http://mytarget/",
    agent: http.globalAgent
});

nicolashenry on 10 Jul 2014

👍4

All 13 comments

@bminer hmm interesting, is there anyway you could add a minimal failing test that reproduces this? That would be the easiest way to see where the potential bug might be.

jcrugzz on 16 Apr 2014

@jcrugzz Sure. I'll try to post back here by Thurs. next week.

bminer on 21 Apr 2014

@bminer was this able to be resolved?

jcrugzz on 8 May 2014

I don't know yet. I am running Node v0.10.15, but I will try 0.10.26 to see if the problem has been fixed.

bminer on 10 May 2014

@bminer its safe to say you should be able to upgrade to v0.10.28 without any problem. Let me know.

jcrugzz on 11 May 2014

@bminer Has your problem gone away since upgrading to 0.10.26? I started seeing this on straight http (no https). If I serve a web page straight from node.js its fine, but if I put it in front of hipache (which uses node-http-proxy) I start getting these ERR_CONTENT_LENGTH_MISMATCH errors for some of my assets. I originally experienced this on 0.10.25, but upgrading to both 0.10.26 and 0.10.28 didn't fix the issue.

jkingyens on 13 May 2014

@jkingyens if you can get a small reproducible example using the latest version of node-http-proxy, I would love to help figure out why might be happening! Failing tests are always a good addition to find a subtle problem :)

jcrugzz on 13 May 2014

@jcrugzz Understandable :) I couldn't isolate it to node-http-proxy. The best I could do was show the problem occurred behind hipache. Without hipache everything was fine. I was using an older version of hipache so I decided to try the latest release and the problem disappeared. But thanks anyway :)

jkingyens on 16 May 2014

FYI net::ERR_CONTENT_LENGTH_MISMATCH and net::ERR_INCOMPLETE_CHUNKED_ENCODING may happen on Node 0.11.13 now. Node 0.11.10 works fine.

Nowaker on 5 Jun 2014

Using globalAgent seems to solve this issue for me :

var http = require('http');
var httpProxy = require('http-proxy');

var proxy = httpProxy.createProxyServer({
    target : "http://mytarget/",
    agent: http.globalAgent
});

nicolashenry on 10 Jul 2014

👍4

Had this problem, too. Upgrading from Node v0.10.8 to v0.10.30 resolved it.