> On 7 Aug 2020, at 17:18, Víctor Enríquez wrote:
>
> Hi,
>
> So we have a service exposing a grpc interface under a certain location
> and we are using nginx in front of it. The config looks like the
> following:
>
> upstream grpcservers {
> server fqdn:port;
> server fqdn:port;
> }
>
> ..
My understanding is that abrupt client disconnects are transparent through
nginx -- the connection to upstream is closed and the upstream should handle
that as it can. Please correct me if I am wrong.
Is there a way to use a call-back (or something similar, a redirect), in
nginx.conf, for client di
Hi,
So we have a service exposing a grpc interface under a certain location
and we are using nginx in front of it. The config looks like the
following:
upstream grpcservers {
server fqdn:port;
server fqdn:port;
}
...
server {
listen port ssl http2;
client_max_body_size 15m;
server_nam
Thank Francis, if you're right, it's a backend problem.
we are solving.
El El jue, 6 de ago. de 2020 a la(s) 10:25, Francis Daly
escribió:
> On Thu, Aug 06, 2020 at 09:48:55AM -0600, Rick Gutierrez wrote:
>
> > El jue., 6 ago. 2020 a las 6:29, Francis Daly ()
> escribió:
>
>
>
> Hi there,
>
>
>
Thanks for the reply and I'm sorry! It was my fault that I didn't see
that text in the documentation.
"These directives are inherited from the previous level if and only if
there are no error_page directives defined on the current level."
On Fri, Aug 7, 2020 at 4:05 AM Francis Daly wrote:
>
> On
On Thu, Aug 06, 2020 at 09:43:46PM -0300, Fabiano Furtado Pessoa Coelho wrote:
Hi there,
> http {
> error_page 502 503 /my503.html;
> ...
> server {
> ...
> error_page 403 =503 /my503.html;
> #error_page 502 503 /my503.html;
> I can solve this issue uncommenting the "#error_pa
