[prev in list] [next in list] [prev in thread] [next in thread] 

List:       cherokee
Subject:    Re: [Cherokee] max age option
From:       Stefan de Konink <skinkie () xs4all ! nl>
Date:       2008-01-05 15:22:10
Message-ID: 477FA0A2.3060201 () xs4all ! nl
[Download RAW message or body]

A.D.F. schreef:
> Stefan de Konink wrote:
>> A.D.F. schreef:
>>> Stefan de Konink wrote:
>>>> Stefan de Konink schreef:
>>>>> I see you have implemented something :) I'll check it out :)
>>>> Set max-age         1, mime type 'application/xml'
>>>>
>>>> It seems it only works on one specific entry (so if two entries are
>>>> present it won't work). It is of course an early attempt, but diversity
>>>> in extention vs mimetype would be appreciated.
>>> I guess some clarification is needed.
>>>
>>> In cherokee configuration file (i.e. /usr/local/etc/cherokee/cherokee.conf)
>>> there should be ONLY ONE LINE specifying ONLY ONE mime file, i.e.:
>>>
>>> server!mime_files = /usr/local/etc/cherokee/mime.types
>>>
>>> NOTE: right now, the first time you install cherokee 0.6.0 trunk,
>>>       you should EDIT the mime.types file and INCLUDE the content
>>>       of mime.compression.types that can be found in the same directory
>>>       where the cherokee mime.types is placed.
>>>
>>> In mime.types file you can use this syntax:
>>>
>>> mime_type     [ .number ]     extension1[, extension2 ... ]
>>>
>>> i.e.:
>>>
>>> image/gif     .300    gif
>>> image/jpeg    .86400  jpeg, jpg, jpe
>>> image/png             png
>>>
>>> Above settings mean:
>>>     - use a max_age value of 300 seconds (5 minutes) for gif files;
>>>     - use a max_age value of 86400 seconds (1 day) for jpeg files.
>>>     - do NOT use any max_age value for png files.
>>>
>>> NOTE: it is likely that in next Cherokee release
>>>       (maybe 0.7, I am not sure yet),
>>>       above .number notation for max_age value will be removed
>>>       from mime.types file and moved to cherokee.conf file
>>>       in order to be handled by new administration interface.
>>>
>>>
>>> Please Stefan, may you resend this message to cherokee@cherokee-project.com
>>> because my ISP filters that address in order to not flood it with SPAM
>>> (I really hope this issue will be solved soon or later).
>> Done :)
>>
>> I figured out the dot notation. But my 'issue' was that i want to have a
>> fast xml and a 'slow' xsl ;)
> 
> Yes, I know that it is a common problem because
> xsl should have its own mime type, i.e.: application/xls+xml
> but (unluckily) it has not been registered yet.
> 
> As a temporary (and not optimal) solution,
> you may try to remove xsl extension from application/xml
> and add it to a new mime type, i.e.:
> 
> text/xml	xsl
> 
> # or even the undocumented
> 
> text/xsl	xsl
> 
> It should work well with most browsers even if it is not granted for all.
> 
> 
> In the last 2 weeks I sent a few emails to discuss
> about when to schedule the requested new features about being able
> to set a max-age value at various levels (server, virtual server,
> mime-type, file extension, directory, etc.).
> 
> I estimated a delay of at least one month for upcoming 0.6.0
> to add and test all above features,
> so I thought to shift those changes to 0.7.x
> and to add only a minimal support in 0.6.0
> (in order to not delay 0.6.0 too much).
> 
> If you think it is useful,
> I could add other two parameters at server level:
> 
>    - server!use_max_age = BooleanValue
>      to enable / disable sending of max-age HTTP header at server level
>      (also setable in new administration interface);
> 
>    - server!max_age = NumericValue
>      to set a default max-age value, so that mime types without
>      a max-age value in mime.types file use that default value anyway
>      (also setable in new administration interface).

Lets say your current 'work around' work perfectly for me. My other two 
bugs related to UserDir authentication and/or relative passwd files are 
not optimal, but not as critical as this one was :)

I personally think that 'server' level is not smart, but directory level is.


Stefan
_______________________________________________
Cherokee mailing list
Cherokee@cherokee-project.com
http://cherokee-project.com/cgi-bin/mailman/listinfo/cherokee
[prev in list] [next in list] [prev in thread] [next in thread]