Closed pecord closed 11 years ago
So i replaced the line that was giving me trouble
var options = util._extend({}, self.options);
in node.js:line 4573 with
var options = self.options;
It got farther but still failed, this time it threw "Uncaught TypeError: Property 'INIT_RESPONSE' of object #
None of the stuff to make request has even been worked on. Underscore.js isn't what you are looking for because it is Node core. HTTPParser isn't fully implemented either, as we just got enough to handle incoming requests.
I kind of assumed it was not fully implemented yet, still figured I should document it. I really like this project idea by the way, i'm a big proponent of the idea of self-hosted and P2P web apps.
Yeah, good to document. The work should be done in the separate repos, though. I have found that most problems have arisen from the net-chromify and http-parser-js libraries since they were completely implemented. http-chromify is essentially a copy of node's http.js with just a few changes to avoid native calls.
I ran into exactly same issue. I am trying to implement a proxy HTTP server which will serve files contained in a Chrome packaged app itself by accessing them using the http://developer.chrome.com/apps/runtime.html#method-getURL API.
This project was just a proof of concept and shouldn't be used for actual projects. Someone released a better version that uses node bindings at https://npmjs.org/package/chromify which should probably be used for your project.
I added the code below to the start of the http example and it threw " Uncaught TypeError: Object #