Hi,
OK, I see. Now I agree that Accept-Ranges header should be removed anyway in
slice module, and any plan to fix that?
Posted at Nginx Forum:
https://forum.nginx.org/read.php?2,288569,288632#msg-288632
___
nginx mailing list
nginx@nginx.org
http://m
Hi,
this is a vm created from the cloud provider. Than i just added the repo of
nginx, the official one.
Than did regular upgrades. Today also i run the yum update and got the
1.19.1 version of nginx.
[root@web ~]# nginx -V
nginx version: nginx/1.19.1
built by gcc 4.8.5 20150623 (Red Hat 4.8.5-39)
Hi,
> On 8 Jul 2020, at 07:14, webber wrote:
>
> Hi,
>
> Thanks for your reply. I have tried the patch that removes the original
> Accept-Ranges in slice filter module, but it is not work as my expected.
> Because I think response header `Accept-Ranges` should be added if client
> send a range
Hi,
Sorry to bother you, I rechange the patch as follow:
Previously, if an Accept-Ranges header was already present in the first
slice
response, client received two copies of this header. Now, the slice filters
removes the Accept-Ranges header for partital request and if original server
respon
On Fri, Jul 03, 2020 at 09:12:56AM -0400, siva.pannier wrote:
Hi there,
> I want all my client applications make call to the service host via proxy.
> And the hosted services are TLSv1.2 enabled. Clients are not in a position
> to upgrade. Hence I want to enforce the SSL encryption when the call
Thank you Francis Daly. Jumping to named location worked in my env also.
I have another issue now:
I want to pass the response body of
http://test.svc.cluster.local:9080/v2/test/* apis to named location
`acreate` which does proxy_pass to another micro-service (which takes the
response of /v2/test
