Never when exposed to public. On the other hand, it is quite common at development test app in non-debug mode, before fiddling with nginx/apache configuration. At least in our region.
If this looks like bug and not intended behavior, would anyone attempt to fix it ? I'd like help myself, but it feels beyond my knowledge of Mezzanine internals. Thanks. > Sounds like there's a bug there when serving static files through Django > in production, but it's no surprise that's gone unnoticed since you should > never be doing this - the public facing web server should be catching all > the static URLs before the Django app is ever hit, for example see the > bundled nginx conf here: > https://github.com/stephenmcd/mezzanine/blob/master/mezzanine/project_template/deploy/nginx.conf.template#L37-L42 > > <https://www.google.com/url?q=https%3A%2F%2Fgithub.com%2Fstephenmcd%2Fmezzanine%2Fblob%2Fmaster%2Fmezzanine%2Fproject_template%2Fdeploy%2Fnginx.conf.template%23L37-L42&sa=D&sntz=1&usg=AFQjCNEphPmTRDGHpsAHlanZGfSgPyK9Rg> > > > -- > Stephen McDonald > http://jupo.org > -- You received this message because you are subscribed to the Google Groups "Mezzanine Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
