Skip to content

Conversation

@nadvorny
Copy link

This is a fix for an issue when mixdown cluster
works behind nginx reversed proxy.
Master process accepted connection and sent it
to workers process. Pipelined http requests were
lost en route.

Browsers did fallback from pipelined mode to
keep-alive only so no issue with browser directly
connecting to mixdown.

This implementation uses cluster built-in socket
sharing and load balancing.

This is a fix for an issue when mixdown cluster
works behind nginx reversed proxy.
Master process accepted connection and sent it
to workers process. Pipelined http requests were
lost en route.

Browsers did fallback from pipelined mode to
keep-alive only so no issue with browser directly
connecting to mixdown.

This implementation uses cluster built-in socket 
sharing and load balancing.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant