[Glass] Nginx , FastCGI and GLASS problem

[Paul DeBruicker]

Those lines from the config just add expiration headers to the files with
extensions in the list.  

I wonder if you change your try_files line to

try_files $uri files/$uri @seaside;

it will do what you want.  Maybe you'll need /files/$uri instead of
files/$uri .  From the docs [1] I'm not sure if nginx will let you prefix
the $uri parameter.  

http://nginx.org/en/docs/http/ngx_http_core_module.html#try_files



Hope this helps

Paul


Mariano Martinez Peck wrote
> Thanks John,
> 
> Yes, I saw his post. I am using a similar configuration. Just a few
> minutes
> ago, I shut down GemStone, start everything again from scratch and somehow
> it seems to work correct now.
> So I don't know what happened hahhaa.
> 
> btw... I noticed these lines:
> 
>         location ~* ^.+\.(css|js|jpg|jpeg|gif|png|ico|svg)$ {
>                 add_header Access-Control-Allow-Origin "*";
>                 expires max;
>                 add_header Cache-Control "public, must-revalidate,
> proxy-revalidate";
>                 add_header Pragma public;
>         }
> 
> 
> I wanted to add that but there is a problem...if the file (say a css) is
> not found in the server (try_files failes), then the request is not
> forwarded to fast_cgi so the file is not loaded at all.
> 
> Is there a way to fallback to /files and use FileLibraries in case those
> fails?  or is it better for production systems to remove the app under
> /files and be sure everything is served by the web server?
> 
> Thanks!





--
View this message in context: http://forum.world.st/Glass-Nginx-FastCGI-and-GLASS-problem-tp4725218p4725249.html
Sent from the GLASS mailing list archive at Nabble.com.