lukechilds/node - node - Gitea: Git with a cup of tea

Author	SHA1	Message	Date
isaacs	5b39929d47	Add --no-deprecation and --trace-deprecation flags	13 years ago
isaacs	260695afd0	http: Hush 'MUST NOT have a body' warnings to debug()	13 years ago
Andreas Madsen	1e0ce5d1bd	domain: the EventEmitter constructor is now always called in nodecore	13 years ago
Simon Sturmer	9a998d5e24	http: don't lowercase http req header until later Don't lowercase the request header until we're in the _addHeaderLine method, makes it easier to intercept the raw request headers.	13 years ago
Shigeki Ohtsu	f721d02c8a	http: fix duplicated variable declaration	13 years ago
Adam Malcontenti-Wilson	4099d1eeba	http: make http.get() accept a URL http.get() now accepts either a URL (as a string) or an options object.	13 years ago
isaacs	faa4d9ff5f	Re-apply http fixes from v0.6 branch properly	13 years ago
Ben Noordhuis	9ae6d8fee3	http: fix client request.end() EPIPE race request.end() would sometimes try to write a zero-length buffer to the socket. Don't do that, it triggers an unnecessary EPIPE when the other end has closed the connection. Fixes #3257.	13 years ago
isaacs	01103d077b	Guard against emitting 'end' twice on http responses Conflicts: lib/http.js	13 years ago
isaacs	a98e845516	Break up huge function in ClientRequest.onSocket Conflicts: lib/http.js	13 years ago
isaacs	14a5b45c06	Guard against emitting 'end' twice on http responses	13 years ago
isaacs	07d8a4650e	Break up huge function in ClientRequest.onSocket	13 years ago
isaacs	8c758e127c	Don't destroy on timeout	13 years ago
isaacs	b4fbf6d275	Fix #3231 . Don't try to emit error on a null'ed req object	13 years ago
Mark Cavage	5871c81181	Add HTTP Status codes from RFC 6585 See: http://tools.ietf.org/html/rfc6585	13 years ago
isaacs	cd8f82c007	Fix incorrect merge choices	13 years ago
isaacs	1de43149bb	http: Clean up parser usage Move parsers.free(parser) to a single function, which also nulls all of the various references we hang on them. Also, move the parser.on* methods out of the closure, so that there's one shared definition of each, instead of re-defining for each parser in a spot where they can close over references to other request-specific objects. Conflicts: lib/http.js	13 years ago
isaacs	0abe42a0f4	http: .once() usage in setTimeout	13 years ago
isaacs	e4dd8dc28e	http leak: Null links from parser to req/res	13 years ago
vvo	5eac8d6739	Fix #3179 HTTP memory leak using ClientRequest.	13 years ago
isaacs	2f93eb6102	http client: Destroy on timeout	13 years ago
isaacs	0a414f4caa	http: Remove socket ondata/onend in parser cleanup	13 years ago
isaacs	9164fa6aaa	Null references to request object on socket errors. Regarding #3199 and #3179 and issues seen in production. Hopefully this fixes them.	13 years ago
isaacs	2fc528ce00	http: Clean up parser usage Move parsers.free(parser) to a single function, which also nulls all of the various references we hang on them. Also, move the parser.on* methods out of the closure, so that there's one shared definition of each, instead of re-defining for each parser in a spot where they can close over references to other request-specific objects.	13 years ago
isaacs	e3ceee2dce	http: .once() usage in setTimeout	13 years ago
isaacs	b7e8e35c0e	http leak: Null links from parser to req/res	13 years ago
vvo	75f2365558	Fix #3179 HTTP memory leak using ClientRequest.	13 years ago
isaacs	c9be1d5ffd	http client: Destroy on timeout	13 years ago
isaacs	bce68134b6	http: Remove socket ondata/onend in parser cleanup	13 years ago
isaacs	bfe9cdb7f2	Null references to request object on socket errors. Regarding #3199 and #3179 and issues seen in production. Hopefully this fixes them.	13 years ago
ssuda	70005be4ff	Fixing ClientRequest setTimeout EventEmitter Leak This will fix #3068	13 years ago
ssuda	48d52d85c3	http, https: fix .setTimeout() Fixes #3107.	13 years ago
Igor Zinkovsky	5ad0140f48	Emit end event only once fixes #2888 Previously a pair of end events would be emitted if a response was paused/resumed, and the underlying socket was closed while the response was paused	13 years ago
Yoshihiro Kikuchi	f82ef0f7c3	http: remove ClientRequest.prototype.pause() ClientRequest.prototype.pause() is not needed. ClientRequest is a writable stream and deferring to OutgoingMessage.prototype.pause() is broken, the method does not exist.	13 years ago
Dmitry Nizovtsev	1e9bcf26ce	net, http, https: add localAddress option Binds to a local address before making the outgoing connection.	13 years ago
Maciej Małecki	da908364a8	tls http https: don't pollute user's `options` object	13 years ago
isaacs	0cdf85e28d	Lint all the JavaScripts.	13 years ago
einaros	83fd1c1de5	Add WebSocket RFC6455 multiheader fields to the http parser.	13 years ago
Ben Noordhuis	2c07712860	http: allow multiple WWW-Authenticate headers	13 years ago
Mark Nottingham	1e425e3fa7	Generate Date headers on responses when not already present.	13 years ago
Ben Noordhuis	6141386f7e	http: allow multiple WWW-Authenticate headers	13 years ago
koichik	c2dc673eb5	http: fix http-parser is freed twice after response to CONNECT/Upgrade request. Fixes #2704.	13 years ago
koichik	3fd13c6426	http: fix free http-parser too early when the status code is 100 (Continue). Fixes #2636.	13 years ago
Brandon Benvie	5403a8ce4c	core: add `NativeModule.prototype.deprecate` Formalize and cleanup handling of deprecated core methods.	13 years ago
Ben Noordhuis	e806ad39d0	net, tls, http: remove socket.ondrain Replace the ondrain hack with a regular 'drain' listener. Speeds up the bytes/1024 http benchmark by about 1.2%.	13 years ago
koichik	a6f3451e25	http: fix test-http-should-keepalive.js is fail `3df7c90` was removed when conflict was resolved.	13 years ago
koichik	3df7c90c30	http: keep-alive should default with HTTP/1.1 server As RFC 2616 says we should, assume that servers will provide a persistent connection by default. > A significant difference between HTTP/1.1 and earlier versions of > HTTP is that persistent connections are the default behavior of any > HTTP connection. That is, unless otherwise indicated, the client > SHOULD assume that the server will maintain a persistent connection, > even after error responses from the server. > HTTP/1.1 applications that do not support persistent connections MUST > include the "close" connection option in every message. Fixes #2436.	13 years ago
Ben Noordhuis	56e34c2f81	http: fix deprecation warning module ID Mea culpa, I told @mmalecki wrong	13 years ago
koichik	35fe3eb5c7	http: reduce creating http-parser instances Fixes #2577.	13 years ago
Maciej Małecki	d5047f5fe6	http: use `util._deprecationWarning` for deprecation warning	13 years ago

1 2 3 4 5 ...