HTTP Parser VS http-proxy

It looks not too different from the majority of HTTP parsers out there written in C. Here is an example of NodeJS [0].

[0] https://github.com/nodejs/http-parser/blob/main/http_parser....

NodeJS's HTTP parser used to be a handwritten C lib: http-parser

Whoa, I didn't know that! But yeah, it seems like https://github.com/nodejs/http-parser is based on nginx. It now uses https://github.com/nodejs/llhttp but has some of the same legacy.

On the other hand, deno's HTTP stuff is built on top of Hyper, a Rust library https://github.com/hyperium/hyper

Boost.Beast has its own HTTP parser[0], during the development of which Vinnie Falco (the principle author of Beast) found many bugs/inconsistencies in Node.js's own parser[1]

[0] https://www.boost.org/doc/libs/develop/libs/beast/doc/html/b...

[1] https://github.com/nodejs/http-parser/issues?q=is%3Aissue+au...

For cases where it is necessary to pass local information to/from a callback, the http_parser object's data field can be used.

Legacy HTTP/1.1 suffers a few issues, see the current RFC errata:

https://www.rfc-editor.org/errata_search.php?rfc=7230&rec_st...

There are issues particularly around how whitespace and obsolete line folding should be handled

https://github.com/nodejs/http-parser/issues?q=is%3Aissue+wh...

https://github.com/httpwg/http-core/issues/53

It's not as trivial as a few string splits.

There's picohttpparser and the one used in node.js: https://github.com/nodejs/http-parser

Take a look at https://github.com/http-party/node-http-proxy , specifically their .web() helper

I have been tasked with writing a proxy server that takes a clients requests and forwards it to a target server (normal proxy stuff). The client and the target are out of my control. The only change in the client is that the its requests to the proxy server instead of the target. Now, what I need to do is modify the response from target because the client expects it in a certain format and the server responds with a different format. I have a working implementation using http-proxy (https://github.com/http-party/node-http-proxy) that works over HTTP . But I need it to work over HTTPS, I can't make much sense of the documentation and I can't find any additional resources on how HTTPS can be implemented. The client-proxy and proxy-target connection both need to be encrypted(HTTPS). I found solutions using different tools but they mostly seem to be encrypted end to end, so the proxy can't read the response data(I need to be able to modify it). Any ideas on how I can do this?

What you're describing is a proxy server. If you wanted to use Node.js check out https://github.com/http-party/node-http-proxy. Notice that the examples there just forward the req though which potentially has identifying information like cookies, so you'll need to rework to anonymize. Should be straightforward.

There's several ways to have a blog path contain a separate setup from the marketing/product routes.

One is to run a reverse proxy on the root domain to pull in separate routes for various services.

https://github.com/http-party/node-http-proxy

You can do rewrites at the server level for the root domain

Or if the app on the root domain can do the routing for you (have done this before with a Rails app)

Check the documentation of the http-proxy-middleware library (and of the node-http-proxy library, used under-the-hood) to learn how you can manipulate the proxied request & response.

Relevant node-http-proxy issue: https://github.com/http-party/node-http-proxy/issues/230

I'm running Node app in Heroku which is using node-http-proxy, and I've given my Heroku app the domain "example.com"