From 20e8cfa2ddaad7c2ca351e1a08487e46f38c6ef8 Mon Sep 17 00:00:00 2001 From: reivilibre Date: Mon, 7 Nov 2022 13:52:31 +0000 Subject: deploy: 42f9d414c266188645ef2a36eeff05309b779a46 --- develop/print.html | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) (limited to 'develop/print.html') diff --git a/develop/print.html b/develop/print.html index d540eab919..cb0dd45d54 100644 --- a/develop/print.html +++ b/develop/print.html @@ -10262,9 +10262,10 @@ have different characteristics and so admins may wish to run multiple groups of workers handling different endpoints so that load balancing can be done in different ways.

For /sync and /initialSync requests it will be more efficient if all -requests from a particular user are routed to a single instance. Extracting a -user ID from the access token or Authorization header is currently left as an -exercise for the reader. Admins may additionally wish to separate out /sync +requests from a particular user are routed to a single instance. This can +be done e.g. in nginx via IP hash $http_x_forwarded_for; or via +hash $http_authorization consistent; which contains the users access token.

+

Admins may additionally wish to separate out /sync requests that have a since query parameter from those that don't (and /initialSync), as requests that don't are known as "initial sync" that happens when a user logs in on a new device and can be very resource intensive, so -- cgit 1.5.1