You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am aware of cluster, but my requirement is I want to isolate workers by host name. For example, I have one application with 5 customers and each one are using same app but different database, so all internal caching etc. must be isolated.
Currently my primary server listens on https and then after inspecting SNI callback server name, I have to proxy entire content to worker process. This is waste of CPU time and memory. And put unnecessary extra http host headers to correctly provide IP of forwarded request.
I am aware that TLS socket cannot be transferred to worker process, but can I transfer the socket at time of SNI callback?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
I am aware of cluster, but my requirement is I want to isolate workers by host name. For example, I have one application with 5 customers and each one are using same app but different database, so all internal caching etc. must be isolated.
Currently my primary server listens on https and then after inspecting SNI callback server name, I have to proxy entire content to worker process. This is waste of CPU time and memory. And put unnecessary extra http host headers to correctly provide IP of forwarded request.
I am aware that TLS socket cannot be transferred to worker process, but can I transfer the socket at time of SNI callback?
Beta Was this translation helpful? Give feedback.
All reactions