Cobalt VS methanol

I'd like to disagree. I'm an high school student myself and I am interested mostly in programming, but also in computer science. I have never studied anything in either fields at school so maybe my opinion here is limited. The first point I'd like to address is that, while the line between computer science and programming is sometimes very thin, this project clearly falls in the latter's territory. Furthermore, being a computer scientist or a software engineer doesn't excuse an individual from not following the coding practices that regulate a particular language. While the latter is a tool in both cases, it's important in my opinion to maximize its expressivity to get the job done as efficiently as possible. At least in my opinion this is very important to understand the difference between the various programming languages, build tools and everything else as, without following the tool's philosophy at heart, they start to look all the same very fast. Finally a computer scientist could have an interest in being a good programmer and vice versa which makes it trivial to start following good practices from the start. At least this is what I've always tried to do from my first project(https://github.com/Auties/MeteorShardSourceCode) to my last ones(https://github.com/Auties00/Reified https://github.com/Auties00/WhatsappWeb4j).

You can find the library here

Methanol - Lightweight HTTP extensions for Java: https://github.com/mizosoft/methanol

https://github.com/mizosoft/methanol - Lightweight HTTP extensions for Java

2) Any response code that is cacheable by default is saved unless forbidden by Cache-Control. Otherwise, the response is cached if headers allow it.