needle - npm Package Compare versions

Comparing version 2.3.2 to 2.3.3

lib/needle.js

		@@ -40,3 +40,3 @@ //////////////////////////////////////////
		// these are the status codes that Needle interprets as redirects.
		var redirect_codes = [301, 302, 303, 307];
		var redirect_codes = [301, 302, 303, 307, 308];

		@@ -43,0 +43,0 @@ //////////////////////////////////////////

package.json

		{
		"name": "needle",
		"version": "2.3.2",
		"version": "2.3.3",
		"description": "The leanest and most handsome HTTP client in the Nodelands.",
		@@ -5,0 +5,0 @@ "keywords": [

README.md

		@@ -395,3 +395,3 @@ Needle

		Unless you're running an old version of Node (< 0.11.4), by default Needle won't set the Connection header on requests, yielding Node's default behaviour of keeping the connection alive with the target server. This speeds up inmensely the process of sending several requests to the same host.
		Unless you're running an old version of Node (< 0.11.4), by default Needle won't set the Connection header on requests, yielding Node's default behaviour of keeping the connection alive with the target server. This speeds up immensely the process of sending several requests to the same host.

		@@ -398,0 +398,0 @@ On older versions, however, this has the unwanted behaviour of preventing the runtime from exiting, either because of a bug or 'feature' that was changed on 0.11.4. To overcome this Needle does set the 'Connection' header to 'close' on those versions, however this also means that making new requests to the same host doesn't benefit from Keep-Alive.

New alerts