build-your-own-x VS forward-proxy

View on GitHub

✅ codecrafters-io/build-your-own-x : https://github.com/codecrafters-io/build-your-own-x

8) Build Your Own X: Unleash your inner inventor and embark on a journey of self-creation with this collection of project ideas for building your own software, tools, and even operating systems. Fuel your entrepreneurial spirit and learn valuable engineering principles by bringing your innovative ideas to life. (https://github.com/codecrafters-io/build-your-own-x)

Also if we can someone merge this level of detail/guidance with the projects on https://codecrafters.io/, i would easily pay for something like that.

Build your own X is another useful resource for a curious mind.

This is what you're looking for: Build your own X!

Agreed. I am not at all against people learning how to do it. But if that's the purpose then it's probably better to present it as such (like the resources at your link does). But the claim that all you need is 100 LOC to make a proxy server work is a bit bogus when you rely on Ruby's standard library. Look at the code at https://github.com/jamesmoriarty/forward-proxy/blob/main/lib.... As expected, it doesn't parse headers but uses stdlib's code to do that. Good, less likely to have bugs. But that means that you can claim that you implemented an HTTP header parser in one line of code:

  req_headers = Hash[req.header.map { |k, v| [k, v.first] }]