Re: WWWOFFLE Version 2.9-beta released

Miernik <[email protected]> writes:

> Andrew M. Bishop <amb-Uxr6IM1mbv2TY6FTCsQk+9Bc4/[email protected]> wrote:
> > Does this option sound useful?  It would be fairly simple to add.
> 
> As an option it sound very usefull. But only optionally of course:
> 
> [<URL-SPEC>]             request-with-cookies-always = yes | no

Yes of course it would be URL specific like the other options in the
OnlineOptions setion.


> However it would be very useful if only text/html MIME type was affected
> by this, not the image/* application/x-javascript or text/css files on
> the same host.

The problem is that WWWOFFLE can only know the MIME type if the
contents of the page are already cached.  If the page is not cached
then there is no way to know what the MIME type is until the reply
comes in and it is too late then.  This is the reason that I have not
added in the ability to treat pages differently depending on the MIME
type.


> BTW I have wwwoffle set up this way in online mode:
> 
> OnlineOptions
> {
> <http://*/*.pdf>         request-changed         = -1
> <http://*/*.pdf>         request-changed-once    = yes
> <http://*/*.pdf>         request-expired         = no
> <http://*/*.pdf>         request-no-cache        = no

...

>                          request-changed         = 0
>                          request-changed-once    = no
>                          request-expired         = yes
>                          request-no-cache        = yes
> }

> BTW Is there maybe a simpler way to code the above config?
> Something like this would be very useful:

> OnlineOptions
> {
> <mime-type = text/html>  request-changed	= 0
> <mime-type = text/html>  request-changed-once	= no
> <mime-type = text/html>  request-expired	= yes
> <mime-type = text/html>  request-no-cache	= yes
> 
>                          request-changed         = -1
>                          request-changed-once    = yes
>                          request-expired         = no
>                          request-no-cache        = no
> }

There is no alternative to having all of these entries since there is
no way of doing this based on the MIME type.  Even if there was
checking based on the MIME type you would need to put multiple MIME
types; text/html, application/xhtml+xml, application/xml, text/xml.


> Besides that: is there anything redundant in the above config?
> Are there really 4 lines needed to do what the above does? Maybe 3 or 2
> for each would be enough, and the effect would be the same? I am not
> really exactly sue how the request-* options work, so I use 4 to be
> sure, but maybe some expert on this can assure me that 3 or 2 of these
> do exactly the same.

The first two options in each group of four will make sure that pages
that you don't want to be refreshed often will only be checked once
when online and the other pages will be checked each time that they
are requested.  You are selecting non-default values for these
specific file extensions so they must be specified.

The second two options in each group make sure that even if the server
asks for the page to be refreshed each time they will not be in the
first case and will be for the second case.  These are the default
values but need to be specifically specified since you want to have
the non-default value for anything that doesn't match specific file
extensions.

-- 
Andrew.
----------------------------------------------------------------------
Andrew M. Bishop                             amb-Uxr6IM1mbv2TY6FTCsQk+9Bc4/[email protected]
                                      http://www.gedanken.demon.co.uk/

WWWOFFLE users page:
        http://www.gedanken.demon.co.uk/wwwoffle/version-2.8/user.html