Response cleanup

"@Raydiation Just the other day you asked if I would review your PRs and now you merged this whole cache thing 1) without asking for advice 2) without listening to the advice given to you.
OOP wise it's beautiful, but usability wise not so much.
You say cache control has nothing to do with the response - cache control has everything to do with the response, as a matter of fact it is one of the most important things about it.
If you really want to separate cache control from the response, then make one class and add the appropriate methods to it: setLastModified(), setExpireAt(), setMaxAge(), `disableCaching()' etc., because atm. if no cache is set no proper cache prevention headers are sent.
But imho they belong in the response class."

Sry yesterday was not my day, also tried testing it and then had to rebase (which didnt work) so I just went "fuck it" and merged.

Did you take a look at the cache classes?