Hello trungaczne,
In your case this is expected behavior. This is because the
$upstream_http_content_type exist only when the upstream already started to
return response to the nginx box. But nginx should determine the caching
policy for current request before any connection to the upstream will
Using "proxy_cache" directive with a variable seems to change that
variable's value.
Tested against a fresh install of nginx 1.9.6 (default configure parameters)
on 2 different Ubuntu:14.04 hosts. DigitalOcean droplets.
The following configuration works as expected: It returns 0/1/2 depending on
This is probably a broken full page ad from an app that you have installed.
Remove any suspicious apps until the problem goes away. A factory reset
will probably work as well.
On Wed, Oct 28, 2015 at 4:26 PM, Shane Duffield
wrote:
> Hello Maxim
>
> I am using Android. The problem is on my phone
On Wednesday 28 October 2015 16:29:55 tamere22 wrote:
> Thanks for your time.
> So you're saying clients request www.siteA.com but rewrite packets to say
> host: www.siteB.com in their http request ?
>
> Why would google bot do such a thing ?
>
> I'm still unsure because I don't see why legitim
Hello Maxim
I am using Android. The problem is on my phone. How do I reset DNS etc on
Android?
Shane
-Original Message-
From: nginx [mailto:nginx-boun...@nginx.org] On Behalf Of Maxim Konovalov
Sent: 28 October 2015 15:41
To: nginx@nginx.org
Subject: Re: nginx on Debian pop-up
Hi Shan
Thanks for your time.
So you're saying clients request www.siteA.com but rewrite packets to say host:
www.siteB.com in their http request ?
Why would google bot do such a thing ?
I'm still unsure because I don't see why legitimate clients would do that.
For you, it's ok to have in log file "
On Wednesday 28 October 2015 15:34:50 tamere22 wrote:
> Hi,
>
> I'm sorry but I can't believe this is true. The random "hosts" I see in logs
> are defined in other "server" blocks that have their own separate log files.
You have a couple of server blocks that listens on different ports.
So for e
Hi,
I'm sorry but I can't believe this is true. The random "hosts" I see in logs
are defined in other "server" blocks that have their own separate log files.
Also why would the "server" information in the logs be good whereas the "host"
information is completly random ?
Please review configurat
Wrong email... I am not able to answer your query! Sorry
-Original Message-
From: nginx [mailto:nginx-boun...@nginx.org] On Behalf Of Valentin V. Bartenev
Sent: 28 October 2015 15:47
To: nginx@nginx.org
Subject: Re: Invalid "host" information in access and error logs
On Wednesday 28 Octo
On Wednesday 28 October 2015 14:36:15 tamere22 wrote:
> Hi,
>
> My message is referring to this bug report :
> https://trac.nginx.org/nginx/ticket/818#comment:6
>
> The person answering me told me to come talk here about this.
>
> I don't understand his answers, as "How nginx processes a reques
Hi Shane,
On 10/27/15 9:25 PM, Shane Duffield wrote:
> Help... for some reason in the last week I constantly get a pop up
> window on my Samsung Galaxy S6. I have attached a screen shot. How
> do I get rid of this annoyance?
>
High probability that you see something described here:
http://nginx.
Hi,
My message is referring to this bug report :
https://trac.nginx.org/nginx/ticket/818#comment:6
The person answering me told me to come talk here about this.
I don't understand his answers, as "How nginx processes a request" page states
"In this configuration nginx tests only the request’s
12 matches
Mail list logo
