Yeah, that fixes the issue. I think I'm more likely to use fully qualified entries in ALLOWED_HOSTS in most cases so that the illegal hosts check is left intact, but it's good to know.
Thanks for your help! On Mon, Oct 31, 2016 at 12:03 PM, Eduardo Rivas <[email protected]> wrote: > Yeah, the server name is working, the problem is that nginx is returning a > 444 (a proprietary error code that means "drop this request altogether" > https://httpstatuses.com/444). Whether or not a 444 is returned depends > on a simple match against an ALLOWED_HOSTS regex, and that will not work > with the dot notation https://github.com/stephenmcd/ > mezzanine/blob/master/mezzanine/project_template/deploy/ > nginx.conf.template#L23-L26 > > Maybe just comment-out that block and see how it goes? That should disable > the checks for illegal hosts on nginx and let everything reach Django. > > > -- > You received this message because you are subscribed to a topic in the > Google Groups "Mezzanine Users" group. > To unsubscribe from this topic, visit https://groups.google.com/d/to > pic/mezzanine-users/ElpLcvVVg8w/unsubscribe. > To unsubscribe from this group and all its topics, send an email to > [email protected]. > For more options, visit https://groups.google.com/d/optout. > -- 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.
