nin wrote:
> Hello!
>
> On Mon, Aug 27, 2018 at 06:56:01PM +0530, Sharan J wrote:
>
> > Hi,
> >
> > Sample conf:
> >
> > http{
> > resolver x.x.x.x;
> > server {
> > server_name _;
> > location / {
> >
Hi,
Sample conf:
http{
resolver x.x.x.x;
server {
server_name _;
location / {
proxy_pass http://somedomain.com;
}
}
I have nameservers configured in my resolv.conf. But, somedomain.com will
be configured in x.x.x.x DNS server only. So, I have specified resolver in
P/2 alone? and not in HTTP/1.1?
Thanks,
Shanthu
On Wed, Aug 9, 2017 at 9:07 PM, Maxim Dounin wrote:
> Hello!
>
> On Wed, Aug 09, 2017 at 08:46:41PM +0530, Sharan J wrote:
>
> > Hello,
> >
> > I am using Nginx as a reverse proxy and have enabled HTTP/2. For a
> >
Hello,
I am using Nginx as a reverse proxy and have enabled HTTP/2. For a
particular request, my back-end server sends a custom 4 digit status code
(say ).
When connecting via HTTP/1.1, the exact status code is returned to the
client but, when connection via HTTP/2, the response headers along
fter a restart (in my case config reload) were websocket connections.
>
> Sent from my iPhone
>
> > On Oct 5, 2016, at 5:59 AM, Sharan J wrote:
> >
> > Hi,
> >
> > While reloading nginx, sometimes old worker process are not exiting
> thereby, entering into &qu
Hi,
While reloading nginx, sometimes old worker process are not exiting
thereby, entering into "uninterrupted sleep" state. Is there a way to kill
such abandoned worker process? How can this process be avoided?
We are using nginx-1.10.1
Thanks,
Santhakumari.V
_
016 at 7:21 PM, Валентин Бартенев wrote:
> On Friday 19 August 2016 18:07:46 Sharan J wrote:
> > Hi,
> >
> > Thanks for the response.
> >
> > Would like to know what happens in the following scenario,
> >
> > Client sets its initial congestion window
t it cause DOS?
Thanks,
Sharan
On Fri, Aug 19, 2016 at 5:28 PM, Valentin V. Bartenev
wrote:
> On Friday 19 August 2016 17:06:41 Sharan J wrote:
> > Hi,
> >
> > Would like to know what timeouts should be configured to mitigate slow
> read
> > attack in HTTP/2.
>
Hi,
Would like to know what timeouts should be configured to mitigate slow read
attack in HTTP/2.
Referred ->
https://trac.nginx.org/nginx/changeset/4ba91a4c66a3010e50b84fc73f05e84619396885/nginx?_ga=1.129092111.226709851.1453970886
Could not understand what you have done when all streams are st
