proxy-chain - npm Package Compare versions

Comparing version 0.1.23 to 0.1.24

build/handler_base.js

@@ -169,3 +169,4 @@ 'use strict';
             this.log('Target socket closed');
-            if (this.srcSocket) this.srcSocket.end();
+            // If socket is closed here instead of response, phantomjs does not properly parse the response as http response.
+            if (this.srcResponse) this.srcResponse.end();
         }
@@ -177,3 +178,4 @@ }, {
             this.log('Target socket ended');
-            if (this.srcSocket) this.srcSocket.end();
+            // If socket is closed here instead of response, phantomjs does not properly parse the response as http response.
+            if (this.srcResponse) this.srcResponse.end();
         }
@@ -180,0 +182,0 @@ }, {

CHANGELOG.md

@@ -0,1 +1,5 @@
+0.1.24 / 2018-02-09
+===================
+- Fixed incorrect closing of ServerResponse object which caused phantomjs to mark resource requests as errors.
+
 0.1.23 / 2018-02-07
@@ -2,0 +6,0 @@ ===================

package.json

 {
   "name": "proxy-chain",
-  "version": "0.1.23",
+  "version": "0.1.24",
   "description": "Node.js implementation of a proxy server (think Squid) with support for SSL, authentication and upstream proxy chaining.",
@@ -5,0 +5,0 @@ "main": "build/index.js",

Fixed alerts

New author

Supply chain risk

A new npm collaborator published a version of the package for the first time. New collaborators are usually benign additions to a project, but do indicate a change to the security surface area of a package.

Found 1 instance in 1 package

Improved metrics

Total package byte prevSize

85111

increased by0.49%

Lines of code

1289

increased by0.16%

Number of medium supply chain risk alerts

6

decreased by-14.29%

No dependency changes