I am using nginx as a reverse proxy and am trying to log some variables set
by apache to nginx log. So certain HTTP response headers are set by apache
(PHP) and then I log them successfully with $sent_http_* variables.
But then I don't want the info to be exposed to outside world so I tried to
rem
Hi,
what about $http_content_length and map this variable with directives
$*_cache_bypass and $*_no_cache.
Cheers,
w
--- Original message ---
From: "trm asn"
Date: 7 October 2014, 17:35:41
> Hi List :
>
> Is there any way to restrict object caching bases on their sizes .
>
>
> For exa
Hi List :
Is there any way to restrict object caching bases on their sizes .
For example:
> 3mb pass through
<3 mb cache in Nginx
Any help/hint will be really appreciable .
Thanks,
tRM
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/m
Maxim Dounin wrote:
> Hello!
>
> On Tue, Oct 07, 2014 at 11:31:56AM +0400, kyprizel wrote:
>
>> Updating patch for the last nginx isn't a problem - we need to hear from
>> Maxim what was the problem with old patch (it wasn't applied that time -
>> why should by applied a new one?) to fix it.
>
Thank you very much for your pointing this out. What are some good starting
points for these figures? Some posts I read even say to disable
buffering...
The value for tcp_abort_on_overflow is set to 0 (in /proc/).
Thank you
Posted at Nginx Forum:
http://forum.nginx.org/read.php?2,253796,253806
Hello!
On Mon, Oct 06, 2014 at 09:06:19PM -0400, imran_k wrote:
> We are trying to act as a proxy for a site within the same DMZ. Things seem
> to work fine, except when there is quite a heavy load. There are many CSS
> assets that just hang upon retrieval. Sometimes the full page comes through;
Hello!
On Tue, Oct 07, 2014 at 11:31:56AM +0400, kyprizel wrote:
> Updating patch for the last nginx isn't a problem - we need to hear from
> Maxim what was the problem with old patch (it wasn't applied that time -
> why should by applied a new one?) to fix it.
http://mailman.nginx.org/pipermail
Updating patch for the last nginx isn't a problem - we need to hear from
Maxim what was the problem with old patch (it wasn't applied that time -
why should by applied a new one?) to fix it.
On Mon, Oct 6, 2014 at 10:25 PM, shm...@riseup.net
wrote:
> calling all patch XPerts !
> calling all patc
