It’s a text/css file. It’s 2331 bytes. Is it too small?
gzip_min_length is set to 1100…
Just wondering.
I did gzip it manually (for gzip_static) and it does work as designed.
But I want to make sure that I’ve got the right configuration down for
normal, non-pre-gzipped files.
On Sat, Aug 23, 2008 at 12:47:22PM -0700, mike wrote:
gzip_disable "MSIE [1-6]\.";
gzip_vary on;
It’s a text/css file. It’s 2331 bytes. Is it too small?
gzip_min_length is set to 1100…
Just wondering.
I did gzip it manually (for gzip_static) and it does work as designed.
But I want to make sure that I’ve got the right configuration down for
normal, non-pre-gzipped files.
oh - i am so stupid. i had “gzip off” in that vhost. i didn’t even
bother checking - i turned gzip off for that host to stop the server
from bothering with worrying about gzip.
css matched by the first location ~* ^.+.(jpg|jpeg|gif|css|png|js|ico|html)$
I fixed it - this is what it looks like now. I keep getting the
location ordering confused. That’s probably the most confusing part of
switching to nginx for me is when something matches multiple
locations/etc… anyway, so far so good!
server {
listen 80;
server_name media.xmike.com;
index index.html;
root /home/mike/web/media.xmike.com/;
gzip off;
location ~* \.css$ {
gzip on;
}
include /etc/nginx/defaults.conf;
include /etc/nginx/expires.conf;
location ~* ^.+\.(jpg|jpeg|gif)$ {
valid_referers none blocked foo.com;
if ($invalid_referer) {
return 403;
}
}
}
BTW, do you really use such indentions ?
If yes, then I understand Python author.
No I have it indented nicely, but some of those were include files,
and I decided to paste the contents of them in so you could see the
entire scope of the server block
css matched by the first location ~* ^.+.(jpg|jpeg|gif|css|png|js|ico|html)$
I fixed it - this is what it looks like now. I keep getting the
location ordering confused. That’s probably the most confusing part of
switching to nginx for me is when something matches multiple
locations/etc… anyway, so far so good!
The logic is following:
maximum match for static locations regardless of order,
it’s very handy: you do not need to think about order;
first match for regex locations, order is important,
it’s not too handy, but there is no choice: there is no way
to define maximal match for regex.
This forum is not affiliated to the Ruby language, Ruby on Rails framework, nor any Ruby applications discussed here.