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

Author	SHA1	Message	Date
Ben Noordhuis	21130c7d6f	lib: turn on strict mode Turn on strict mode for the files in the lib/ directory. It helps catch bugs and can have a positive effect on performance. PR-URL: https://github.com/node-forward/node/pull/64 Reviewed-By: Colin Ihrig <cjihrig@gmail.com> Reviewed-By: Fedor Indutny <fedor@indutny.com>	10 years ago
Ben Noordhuis	150d6f1249	lib: http: poison parser references after freeing Make it a little harder to slip in use-after-free bugs by nulling out references to the parser object after handing it off to freeParser(). Reviewed-by: Trevor Norris <trev.norris@gmail.com>	10 years ago
Alex Kocharin	b9960eefc2	http: fix bailout for writeHead Reported-by: Jackson Tian <shyvo1987@gmail.com> Reviewed-by: Trevor Norris <trev.norris@gmail.com>	10 years ago
Fedor Indutny	73343d5cee	http: remove unused code block fix #7769 Signed-off-by: Fedor Indutny <fedor@indutny.com>	11 years ago
Yazhong Liu	ab50fad63b	http: add 308 status_code, see RFC7238 Signed-off-by: Fedor Indutny <fedor@indutny.com>	11 years ago
Yuki KAN	006d42786e	lib: use triple equals Signed-off-by: Trevor Norris <trev.norris@gmail.com>	11 years ago
David Björklund	b105997193	http: avoid duplicate keys in writeHead Use setHeader in writeHead to avoid sending duplicate headers Fixes #5036	11 years ago
Patrik Stutz	54910044b3	http: add statusMessage Now the status message can be set via req.statusMessage = 'msg';	11 years ago
isaacs	085dd30e93	http: provide backpressure for pipeline flood If a client sends a lot more pipelined requests than we can handle, then we need to provide backpressure so that the client knows to back off. Do this by pausing both the stream and the parser itself when the responses are not being read by the downstream client. Fix GH-6214	11 years ago
isaacs	7c9b607048	http: Consistent 'finish' event semantics In other Writable streams, the 'finish' event means that all of the data was written, and flushed to the underlying system. The 'prefinish' event means that end() was called, and all of the data was processed, but not necessarily completely flushed. This change brings the http OutgoingMessage classes more in sync with the other Writable classes throughout Node. Unfortunately, this change highlights an issue with http IncomingMessages, where the _dump() method will not actually pull the data off the wire. This is a minor issue that is typically only relevant in test cases, and will be addressed in the next commit.	11 years ago
isaacs	da93d6adfb	http: Add write()/end() callbacks	11 years ago
isaacs	967b5dbb45	http: Use streams3 directly, not .ondata/end	11 years ago
isaacs	22c68fdc1d	src: Replace macros with util functions	11 years ago
Ben Noordhuis	0330bdf519	lib: macro-ify type checks Increases the grep factor. Makes it easier to harmonize type checks across the code base.	11 years ago
isaacs	831de7cbb9	http: Use OOP for OutgoingMessage._finish Sniffing instanceof a child class in the parent class's method is Doing It Wrong.	12 years ago
Trevor Norris	278183a902	{stream,udp,tls}_wrap: remove unused offset/length The function arguments offset and length are now no longer used since all I/O requests now use discretely allocated memory.	12 years ago
Trevor Norris	88333f7ace	http: don't slice unless necessary The incoming Buffer was being sliced just to possibly not be used. Instead place the .slice inside the conditional to not be created unless necessary.	12 years ago
Timothy J Fontaine	6717fdccb4	http: move Server and ServerResponse out	12 years ago