Channels: Sudden & Mysterious 400 Bad Request

[jamie...@ilq.com]

I'm using Nginx -> Daphne -> Redis -> manage.py runworker. Nginx and daphne are both producing a 400 Bad Request to simple GET requests. I'm not seeing the request in the worker log (-v 3). Redis answers to `redis-cli ping`.

Daphne logs look like it just served the request normally. Worker logs are empty.

I'm trying this both through a browser against nginx, and through curl against daphne directly. Identical responses.

I thought it I had it working, but I guess I broke it.

[Andrew Godwin]

I don't really know what's going wrong then, I guess - 400 Bad Request is not something you'd get from misconfiguration usually. Do you get it from Nginx serving a static file too, or just when it proxies through?

Andrew

--
You received this message because you are subscribed to the Google Groups "Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscribe@googlegroups.com.
To post to this group, send email to django...@googlegroups.com.
Visit this group at https://groups.google.com/group/django-users.
To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/19fc5466-014f-4566-a172-346e5c4381e2%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.