No, 503 may be a legitimate error from upstream that nginx needs to pass to
client.
I am thinking some unused code , say, 590.
On Thursday, December 10, 2015, B.R. wrote:
> Like... 503?
> To me 'server wants to make another upstream dealing with the request'
> sounds very much like 'Service Unav
Like... 503?
To me 'server wants to make another upstream dealing with the request'
sounds very much like 'Service Unavailable'.
---
*B. R.*
On Thu, Dec 10, 2015 at 5:34 PM, Frank Liu wrote:
> Hi
>
> There are a few options for when to try next upstream :
> http://nginx.org/en/docs/http/ngx_http
Sorry to bother everyone. Nginx proxies everything just fine. The issue was
at the upstream side.
Posted at Nginx Forum:
https://forum.nginx.org/read.php?2,263391,263406#msg-263406
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman
Hello Maxim,
Thank you for the response. I was assuming the error_log in the block
was properly set up but apparently it was not. I finally got an error
message "2015/12/10 18:02:13 [error] 30341#0: *10 recv() failed (104:
Connection reset by peer) while reading response header from
upstream". Pro
Hi
There are a few options for when to try next upstream :
http://nginx.org/en/docs/http/ngx_http_proxy_module.html#proxy_next_upstream
Is it possible to configure a custom http code so that upstream servers can
send that code if it wants to send nginx to upstream ?
Thanks
Frank
Hello!
On Thu, Dec 10, 2015 at 05:21:23AM -0500, jonefee wrote:
> i am using nginx as a reverse proxy server(Let 's call it Server A). server
> A's upstream server is also a nginx server((Let 's call it Server B) backend
> with a jetty server((Let 's call it Server C) served at port 8080. we hav
Hello!
On Thu, Dec 10, 2015 at 03:31:23PM +0100, Lukas Tribus wrote:
> >>> It only can be useful for proxying big amounts of data without any
> >>> processing. But if you need compression, or TLS, or SSI, or even some
> >>> simple substitution, then splice() cannot be used.
> >>>
> >> It should f
Hi Maxim,
>>> It only can be useful for proxying big amounts of data without any
>>> processing. But if you need compression, or TLS, or SSI, or even some
>>> simple substitution, then splice() cannot be used.
>>>
>> It should fit in our stream quite nicely.
>
> Not really, as stream is able to d
Hello!
On Thu, Dec 10, 2015 at 01:15:27AM +0300, Maxim Konovalov wrote:
> On 12/9/15 2:54 PM, Valentin V. Bartenev wrote:
> > On Tuesday 08 December 2015 20:50:47 Aleksandar Lazic wrote:
> >> Dear developer.
> >>
> >> Do you know the splice() feature in Linux?
> >>
> >> https://lwn.net/Articles/1
i am using nginx as a reverse proxy server(Let 's call it Server A). server
A's upstream server is also a nginx server((Let 's call it Server B) backend
with a jetty server((Let 's call it Server C) served at port 8080. we have
a lot of Server A and each one of them use the same bunch of server B
10 matches
Mail list logo