'''Make 403 errors easier to identify where and why they happen''' It should be possible to find out where and why 403 errors (Permission denied) occur. The applied patch log the reasons and drop the makeForbidden403 general purpose function. That should surely not be `logging.info` but if anything `logging.debug`. -- JohannesBerg <> I've checked the code to get a feeling what is logging.debug and logging.warning and decided against both. There are no design rules for which logging level should be used in which case. The current implementation have to investigated in hope to understand the concept. For me it looks like logging.debug is used to track program execution. logging.warning if an unexpected proplem occur. I've decided to use logging.info because it's a configuration issue if access is forbidden so the administrator is able to find the reason easy and quick. -- RaphaelBossek <> But the default log level is "INFO" which means that in the much more common case that the administrator actually did intend to block access to a file with ACLs, the log will be spammed with these messages making it essentially useless. -- JohannesBerg <> ---- {{attachment:RaphaelBossek-DetailedForbiddenReasons.patch}} ---- CategoryFeaturePatched