[Neos] Expires header for resources in Neos site

[Visay Keo]

Hi Marcin,

Yes, I need it for Apache web server. Actually I'm wondering how people 
manage different kind of resources' header like js, css, image format. I 
currently use grunt to compile my js/css to name with a timestamp but 
still I need to adjust the name in my css/js include section. For user 
upload images, I use apache module page speed to help with compression 
and automatic expire header settings.

What I was looking for is the a way to do them from Neos without 
external party.

Cheers,
Visay

On 26 តុលា 2014 00:16, Marcin Ryzycki wrote:
> Does it have to be for Apache?
> It's pretty simple on Nginx. In the server {} context you add:
>
> location ~* \.(?:jpe?g|gif|png|ico|swf|svg|eot|ttf|otf|woff|htc|css|js)$ {
>   expires max;
> }
>
> Which sets Expires and Cache-Control headers. Then the next request to
> sample .css file results with:
>
> HTTP/1.1 304 Not Modified
> Server: nginx
> Date: Sat, 25 Oct 2014 17:09:30 GMT
> Last-Modified: Fri, 24 Oct 2014 23:27:30 GMT
> ETag: "544ae062-24698"
> Expires: Thu, 31 Dec 2037 23:55:55 GMT
> Cache-Control: max-age=315360000
>
> M.
>
> On 2014-10-23 07:50:57 +0000, Visay Keo said:
>
>> Hello,
>>
>> Does anyone has a practice of managing expire header for neos site's
>> resources?
>>
>> What would you add to Web/.htaccess <IfModule mod_expires.c> section?
>>
>> Cheers,
>> Visay
>
>

-- 
TYPO3 .... Inspiring People To Share!
Participate: http://typo3.org/participate/