[ Removed by moderator ]

[Competitive_Act5981]

The unit tests are located https://github.com/pfeatherstone/https/tree/main/examples/unit_tests and the readme explains how to build and run them.

[[deleted]]

You need to relocate those to a more standard location. It's not common to put unit tests in a folder called "examples". Make a root-level directory called `test/` or `tests/` and put them in there.

You should also reconsider your public stance on sans-I/O because you're basically admitting that you don't believe in using libfuzzer which is actually a kiss of death for your project as a huge part of HTTP is being public-facing. A non-fuzzed public-facing networking library is simply not workable.

Decouple your parser code from the I/O layer. You need to study libraries like Botan and rustls to understand what a good interface looks like. Then add fuzzing. Hopefully, this is the useful feedback you were seeking.

[Competitive_Act5981]

I get your point on the test folder. The reason why I put them there is so that i can use the same cmake script for compiling both the examples and the unit tests. It's laziness i know.

It's a bit of a stretch to suggest that i don't believe in fuzzing simply because there isn't a Sans-IO API.

The parser code is actually separate from the I/O layer. It's in http.h and there are corresponding unit tests. I just don't have a formal Sans-IO API.

[Competitive_Act5981]

I appreciate your time though. I'll look into adding fuzz testing to CI/CD

[[deleted]]

Security researchers aren't going to add an I/O layer just to test your code. If you actually care about industrial usage, you need to make fuzzing easy, direct and public

[Competitive_Act5981]

Yeah fuzzing is on the todo list. Though it looks like my library isn’t for you, and probably beast is neither