Hi Anto.
Am 24-02-2017 19:03, schrieb Anto:
Hi Team ,
Would like to know how i can configure Ngnix LB with SSL termination ?
In addition to the above would like to configure LB with multiple
httpd's with single IP.
Can you guide me how i can do the same with proxy pass ?
Note : I have a sin
Hi Team ,
Would like to know how i can configure Ngnix LB with SSL termination ?
In addition to the above would like to configure LB with multiple httpd's
with single IP . Can you guide me how i can do the same with proxy pass ?
Note : I have a single OHS server with 2 different httpd.conf files
Hello!
On 02/24/2017 07:33 PM, 0liver wrote:
> We've recently started delivering image urls with query strings for
> cropping, like
>
> http://images-camping.info/CampsiteImages/116914_Large.jpg?width=453&height=302&mode=crop
>
Try add:
proxy_ignore_headers Cache-Control Expires;
Ref:
http:/
We don't explicitly set the proxy_cache_key - we use the default value
provided by NGINX.
>From the docs at
http://nginx.org/en/docs/http/ngx_http_proxy_module.html#proxy_cache_key I
understood that the query string is part of the cache key - I'm reaching out
for help because it doesn't work as I'
Hi Oliver!
How is your proxy_cache_key configured?
Um abraço,
NM
2017-02-24 9:33 GMT-03:00 0liver :
> We've recently started delivering image urls with query strings for
> cropping, like
>
> http://images-camping.info/CampsiteImages/116914_Large.
> jpg?width=453&height=302&mode=crop
>
> We've
We've recently started delivering image urls with query strings for
cropping, like
http://images-camping.info/CampsiteImages/116914_Large.jpg?width=453&height=302&mode=crop
We've also successfully been using the NGINX cache for our images *before*
adding the query strings.
Unfortunately, with th
Hello everybody,
I have installed a dedicated server for NGINX based on Ubuntu Core
I want to define this behavior
NGINX Server (Public IP) >>> listening on port 80 >>> redirect to a LAN
Server on port 80 (http://mylocalserver/virtualhost1)
NGINX Server (Public IP) >>> listening on port 81 >>>
I think from my understanding the proxy_http_version 1.1; is ignored over
https since everything works and that directive does what it states
proxy_HTTP_version for unsecured requests only it will be version 1.1 so i
don't think it has any negative impact on HTTP2/SSL.
Posted at Nginx Forum:
http
So the Nginx documentation says this
http://nginx.org/en/docs/http/ngx_http_upstream_module.html#keepalive
For HTTP, the proxy_http_version directive should be set to “1.1” and the
“Connection” header field should be cleared:
upstream http_backend {
server 127.0.0.1:8080;
kee