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

Author	SHA1	Message	Date
jed	a9ea21feb4	fixed check on header type, to check member instead of object.	15 years ago
Ryan Dahl	7719ce33db	New http-parser No longer based on Ragel, but hand-written. Had to add HTTPConnection.resetParser() because the parser is stricter and will error out when you try to give it a message after the previous had "Connection: close". The HTTP client was doing that. Thus we reset the parser manually after each new connection.	15 years ago
Ryan Dahl	1eba0cadc1	Revert "Normalize HTTP headers." This reverts commit `f623fd7658`. But only the changes made in lib/ they were falsely detecting outgoing headers.	15 years ago
Felix Geisendörfer	bffee5eda4	Bugfix for sendBody() and chunked utf8 strings Http expects chunked byte offsets and ignores the encoding specified in the header. This patch makes node behave accordingly. Bug report: http://groups.google.com/group/nodejs/browse_thread/thread/ab701d49cb059317	15 years ago
Ryan Dahl	43121c15be	API: rename process.inherits to sys.inherits	15 years ago
Ryan Dahl	51c1526b6a	Revert "Upgrade http parser, change node as needed." Something is broken in how keep-alive is working. Reverting until I can fix it. This reverts commit `b893859c34`.	15 years ago
Ryan Dahl	8ad47c8de7	Expose http.IncomingMessage and http.OutgoingMessage	15 years ago
Ryan Dahl	60131fc88c	Expose http.ClientRequest and http.ServerResponse	15 years ago
Ryan Dahl	7a2e784ad7	Module refactor - almost CommonJS compatible now API change summary: * require("/sys.js") becomes require("sys") * require("circle.js") becomes require("./circle") * process.path.join() becomes require("path").join()	15 years ago
Ryan Dahl	ad0a4cefb8	Namespace EVERYTHING under process; introduce GLOBAL http://groups.google.com/group/nodejs/browse_thread/thread/1034fd2ad2cd93e8	15 years ago
Ryan Dahl	910c627fc6	Revert "Change HTTP back to a 1.1 client." This reverts commit `9a70abbf13`.	15 years ago
Ryan Dahl	9a70abbf13	Change HTTP back to a 1.1 client. This was modified in `b893859c34` even though it wasn't really required. Some users are experiencing problems after changing to 1.0 - once those are identified the client will returned to 1.0.	15 years ago
Ryan Dahl	b893859c34	Upgrade http parser, change node as needed. The latest version of http-parser is a bit more stringent EOF semantics.	15 years ago
Ryan Dahl	2b8ab7e24f	utils.js links to sys.js instead of other way around	15 years ago
Ryan Dahl	f623fd7658	Normalize HTTP headers. "Content-Length" becomes "content-length".	15 years ago
Ryan Dahl	522909bcbf	Parse queryString into req.uri.params	15 years ago
Ryan Dahl	e2b7902469	Don't use parseUri for HTTP server The big parseUri RE was showing up often in profiles - this is simpler and yields better performance by taking advantage of the C http parser.	15 years ago
Ryan Dahl	7b337096c9	Add a third argument to http.cat to specify req headers.	15 years ago
isaacs	45f5402446	Pass the Host header in http.cat calls, if it was specified in the URL passed to http.cat.	15 years ago
Ryan Dahl	cda659a8c8	Camel-case all http events	15 years ago
Ryan Dahl	f6657c3c9d	Move http library to /http.js	15 years ago
Ryan Dahl	07792afe0a	Remove "raw" encoding. Rename "raws" to "binary". Deprecation warnings have been added to help the conversion to this new API.	15 years ago
Ryan Dahl	9db2e5f375	Default to utf8 encoding for node.fs.cat()	15 years ago
Ryan Dahl	4f98e2deb3	Fix buffering logic for HTTP outgoing messages. Was sending two packets instead of one for some short messages, and even 3, for short chunked-encoded messages. Also use the more general Encode() function for receiving HTTP bodies. Gives ~6% improvement on "hello world" web server benchmarks.	15 years ago
Ryan Dahl	d1a13bdd35	Fix default encoding for outgoing HTTP messages Was causing send() to throw argument errors because arrays of ints would get paired with the "raws" encoding. The bug was introduced in `8eb1294`.	15 years ago
Ryan Dahl	8eb1294f87	Bugfix: sendBody wasn't setting encoding	15 years ago
Ryan	dbe116ddfe	API: Change arguments of emit(), emitSuccess(), emitError() Instead of myemitter.emit("event", [arg1, arg2, arg3]); the API is now myemitter.emit("event", arg1, arg2, arg3); This change saves the creation of an extra array object for each event. The implementation is also slightly more simple.	15 years ago
Ryan	9dbd92476e	Bugfix: Trap exceptions in URIParser. A user was able to crash chat.tinyclouds.org by sending it a malformed URL! Not good.	15 years ago
Ryan	116f4dea05	lint	15 years ago
Ryan	316e2833f0	Use flat object instead of array-of-arrays for HTTP headers. E.G. { "Content-Length": 10, "Content-Type": "text/html" } instead of [["Content-Length", 10], ["Content-Type", "text/html"]]. The main reason for this change is object-creation efficiency. This still needs testing and some further changes (like when receiving multiple header lines with the same field-name, they are concatenated with a comma but some headers ("Content-Length") should not be concatenated ; the new header line should replace the old value). Various thoughts on this subject: http://groups.google.com/group/nodejs/browse_thread/thread/9a67bb32706d9efc# http://four.livejournal.com/979640.html http://mail.gnome.org/archives/libsoup-list/2009-March/msg00015.html	15 years ago
Kevin van Zonneveld	8489bdbaeb	Buggy connections could crash node.js. Now check connection before sending data every time http://groups.google.com/group/nodejs/browse_thread/thread/16abfa87c32408f3 We have our node.js server monitored by monit, however it seems monit is pretty agressive / quick about closing its connection and thus we've gotten into a loop of errors like this: at #<a ServerResponse>.flush at #<a ServerResponse>.sendBody at [object Object].json at [object Object].[anonymous] at [object Object].[anonymous] at [object Object].[anonymous] http.js:353: Socket is not open for writing connection.send(out, out.encoding); ^ Below is a patch that basically cause flushMessageQueue to check the connection state for each item in the queue rather than just a single time in the beginning.	15 years ago
Ryan	368ea93bfe	Upgrade evcom - fix API issues.	15 years ago
Ryan	7aaab320b3	API: tcp.Connection "disconnect" event renamed to "close". More semantic, since the event will be emitted on connection error, when the connection was ever established.	15 years ago
Ryan	af40ae6b8f	Remove debugging messages in HTTP client	15 years ago
Ryan	3b0408ec1c	Sync evcom after refactor; fix binding issues	15 years ago
Ryan	0638a3a3ab	Add IncomingMessage.prototype.pause() and resume().	15 years ago
Ryan	b27f8ba06d	Default to chunked for client requests without C-Length. Also add test. Reported by Felix Geisendörfer.	15 years ago
Ryan	eb10553634	Move node.inherit, node.path, node.cat to new file: util.js	16 years ago
Ryan	56c785ceae	small clean ups to http.js	16 years ago
Ryan	ef09b2c65d	large http.js refactor	16 years ago
Ryan	216e6204f0	http: Add IncomingMessage as abstract base class of ServerReq ClientRes	16 years ago
Ryan	996d5ef5f1	Add res.client to ClientResponse	16 years ago
Joshaven Potter	4b9f26c51a	validate js	16 years ago
Ryan	d428eff023	Snakecase events .	16 years ago
Ryan	65324866bc	Implement Promises for file i/o	16 years ago
Ryan	ed926da691	Remove onEvent compatibility	16 years ago
Ryan	70fe920fb5	Use events for all HTTP messages. This is a rather large refactor! Mostly for the better side. I've had to remove some functionality like req.interrupt(). A lot of other work is left messy or incomplete.	16 years ago
Ryan	20c0e1fdfb	events for http.Server	16 years ago
Ryan	ed3d6a63d5	Further expand EventEmitter to TCP and HTTP The constructor for TCP servers can no longer take a connection handler for purely technical reasons. (The constructor for EventEmitter is implemented in C++ but addListener is in javascript, and I don't want to make too many C++ -> Javascript references.) Thus I introduce new constructor methods to ease the creation of the servers: node.tcp.createServer() node.http.createServer() These work almost the same as the old constructors. In general we're working towards a future where no constructors are publicly exposed or take arguments. The HTTP events like "on_uri" are not yet using the event interface. onMessage still is a constructor - but this will change soon.	16 years ago
Ryan	dce072a67e	lint	16 years ago

... 4 5 6 7 8