Good day!
We have an Institutional Repository server that uses NGINX as load balancer
but we encountered problem when trying to upload documents to the
repository. It only accepts maximum of 128 kb of data, but the
client_max_body_size 500M;. Is there a way to locate the cause of error.
Here are
On Fri, 19 Apr 2024 03:14:44 +0200,
Fabiano Furtado Pessoa Coelho wrote:
>
> Please, can you spot these overheads in proxying?
>
Establishing and accepting a brand new connection, writing and reading of
requests. Maybe buffering. A lot of useless context switching between
user and kernel spaces.
Hello
As I understand we better replace all proxy_pass to pass when upstream
server is localhost, but pass does not work with remote upstreams.
Is that right?
Sébastien
Le ven. 19 avr. 2024 à 09:38, Kirill A. Korinsky a
écrit :
> On Fri, 19 Apr 2024 03:14:44 +0200,
> Fabiano Furtado Pessoa Coe
On Fri, 19 Apr 2024 10:02:00 +0200,
Sébastien Rebecchi wrote:
>
> As I understand we better replace all proxy_pass to pass when upstream
> server is localhost, but pass does not work with remote upstreams.
> Is that right?
>
It depends on your use case I guess.
Frankly speaking I don't see any r
> It only accepts maximum of 128 kb of data, but the client_max_body_size
> 500M;. Is there a way to locate the cause of error.
Can you actually show what the "error" looks like?
The default value of client_max_body_size is 1M so the 128Kb limit most likely
comes from the backend application o
