I'm trying to get uwsgi and nginx to play nice. After moving to "file sockets" (hopefully I'm using the right terminology here) from TCP sockets, the only thing I get from uwsgi is a 400 with no helpful logging info. I'd like to inspect what exactly nginx is sending uwsgi. How do I do that? Everything I've read so far about bash and sockets relates to TCP or UDP connections.
My assumption is that nginx is unable to write to the file socket at all or at least properly, so I'd like to "inspect" the file socket to see what, if anything, is being written there.
Ideally I'd like a
tail -f equivalent to point at the socket file.
If this assumption wasn't correct that would mean either my browser is sending a malformed request (HIGHLY unlikely IMO, using Chrome) OR uwsgi is incorrectly reporting the nature of the error OR I'm misunderstanding the meaning of an HTTP 400 error. Are any of these a possible cause of the problem?