> Am 14.02.2017 um 22:07 schrieb Ebayer Ebayer :
>
> I want to cache critical files indefinitely regardless of them being hot or
> stale until they're purged (by the app).
>
If you have enough RAM, they will stay cached.
Do you also want to do the memory-management of your apps, allocating
On Tue, Feb 14, 2017 at 09:07:46PM +, Ebayer Ebayer wrote:
Hi there,
> I want to cache critical files indefinitely regardless of them being hot or
> stale until they're purged (by the app).
It still doesn't sound like a task for nginx to me.
If you want your OS file-cache to do busy-work to
I want to cache critical files indefinitely regardless of them being hot or
stale until they're purged (by the app).
Thanks
On Feb 15, 2017 4:30 AM, "Rainer Duffner" wrote:
Am 14.02.2017 um 21:25 schrieb Ebayer Ebayer :
Is there a more deterministic way besides fully trusting the MMU? I reall
It appears it had nothing to do with the includes but what I had in my server
blocks. If I put a particular https server include above another it broke one.
I made 1 of the https server blocks as the default.
From: nginx [mailto:nginx-boun...@nginx.org] On Behalf Of Cox, Eric S
Sent: Tuesday, Fe
> Am 14.02.2017 um 21:25 schrieb Ebayer Ebayer :
>
> Is there a more deterministic way besides fully trusting the MMU? I really
> don't think the MMU will execute well on what I'm setting to accomplish. Some
> more info:
>
> * I run Linux 2.6.32 (RH's)
>
> * I don't trust /dev/shm as a memory
Is there a more deterministic way besides fully trusting the MMU? I really
don't think the MMU will execute well on what I'm setting to accomplish.
Some more info:
* I run Linux 2.6.32 (RH's)
* I don't trust /dev/shm as a memory store
* I want the kernel to keep files cached for a pre determined
In my main nginx.conf file I am doing an include for various files to include
multiple server blocks (1 block per file) If I use a wildcard include the
https servers break but the http server is fine Example
include /servers/*;
this would include 3 server blocks
1 http
2 https
If
> Am 14.02.2017 um 20:10 schrieb Ebayer Ebayer :
>
> Hi,
>
> I have Nginx running as a webserver (not as proxy). I need to cache static
> files that are under /var/www/html/images in memory. What's the simplest way
> to do this?
Your OS does that for you.
That’s why it does not make sense
On Tue, Feb 14, 2017 at 07:10:13PM +, Ebayer Ebayer wrote:
Hi there,
> I have Nginx running as a webserver (not as proxy). I need to cache static
> files that are under /var/www/html/images in memory. What's the simplest
> way to do this?
Don't do anything special in nginx.
Make sure that y
Hi,
I have Nginx running as a webserver (not as proxy). I need to cache static
files that are under /var/www/html/images in memory. What's the simplest
way to do this?
Thank you
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/lis
Changes with nginx 1.11.10 14 Feb 2017
*) Change: cache header format has been changed, previously cached
responses will be invalidated.
*) Feature: support of "stale-while-revalidate" and "stale-if-error"
extensions in the "Cache-Contro
On Tue, Feb 14, 2017 at 04:09:10PM +0800, he.hailo...@zte.com.cn wrote:
> now I understand the duplicate listen ports configured in the http
> block can be used to implement virtual hosts.
>
>
> but what's the purpose to allow this in the stream block? in my
> practise (with 1.9.15.1), nginx will r
now I understand the duplicate listen ports configured in the http block can be
used to implement virtual hosts.
but what's the purpose to allow this in the stream block? in my practise (with
1.9.15.1), nginx will randomly select a backend to serve the tcp/udp request
which seems useless.
b.
now I understand the duplicate listen ports configured in the http block can be
used to implement virtual hosts.
but what's the purpose to allow this in the stream block? in my practise (with
1.9.15.1), nginx will randomly select a backend to serve the tcp/udp request
which seems useless.
b.
14 matches
Mail list logo
