Nginx can't (to my knowledge) easily switch on the Upgrade header without
extra modules as you need to take the header, lowercase it, and check it
equals "websocket", and Nginx if statements are weird and limited in some
important ways.
Instead, I recommend you do prefix-based proxying, like this:
I think you can do conditionals on your server block and proxy pass to the
correct upstream depending on your logic
On Thu, Jan 19, 2017 at 2:18 PM, Dev App wrote:
> There's not individual documentation for every situation because people's
>> choice of webserver and their OS versions and envir
>
> There's not individual documentation for every situation because people's
> choice of webserver and their OS versions and environments differ. If you
> tell me what you're using I can try and provide some hints or links to
> examples.
I thought it would be easy now, since I understand t
Thank you for the answers.
It helps me immensely.
So in theory, if client doesn't need to send data to server (something
which runworker needs to work on),
I only need
nginx --- wsgi -- django
/
nginx --- asgi redis ---/
where Dja
On Wed, Jan 18, 2017 at 12:33 AM, Dev App wrote:
>
> I hope there 's a documentation how to do "running-asgi-alongside-wsgi"
> https://channels.readthedocs.io/en/stable/deploying.html#
> running-asgi-alongside-wsgi
> (I tried google, but none found for how to do it)
>
> I'm just afraid to hand ov
I hope there 's a documentation how to do "running-asgi-alongside-wsgi"
https://channels.readthedocs.io/en/stable/deploying.html#running-asgi-alongside-wsgi
(I tried google, but none found for how to do it)
I'm just afraid to hand over every request to asgi which I don't know much
about.
I hav
6 matches
Mail list logo
