4 ms·
It likely writes request logs to disk as part of the request!
by gregoryl 2y ago
It likely writes request logs to disk as part of the request!
- TZubiri 2y agoI'm having trouble imagining a system where inability to log causes a failure to serve the request instead of just not logging the request. Surely generic servers like apache, nginx handle that case gracefully. It probably isn't a handcoded server in python or something like that, because it is returning a precise status code and message instead of just converting a write() exception to a generic 500. It's an amazing feat of engineering to get this so wrong.
- Joker_vD 2y agoWhy on earth would you want to keep serving requests you can't log?! That makes about as much sense as serving empty pages when your DB/file storage with site contents goes away.
- TZubiri 2y agoIs this trolling? So that users can read the content...
- Joker_vD 2y agoNo, I am serious. If you bother to log the requests, then obviously you care about the logs being accurate and complete. Conversely, if you don't care about the logs, just turn them off entirely. > So that users can read the content... Does e.g. your authorization middleware adopt the same stance?
- TZubiri 2y ago" If you bother to log the requests, then obviously you care about the logs being accurate and complete. Conversely, if you don't care about the logs, just turn them off entirely" Try to log, if not, serve anyways, anything else is insane for a static website. Take a law firm's website, you would rather not serve the webpage because the disk is full? I'm getting all your clients bro.