Messages

1

HFS ~ HTTP File Server / Re: Controlling the Cache-Control header

« on: August 26, 2017, 07:03:34 PM »

And those of that half who know him refuse to use it to differentiate themselves from their compatriots of the south 

Something like that

{.add header|Cache-Control: must-revalidate, max-age=-1, public.}

This doesn't work either.

I have written my own PHP file to list files recursively. It performs the same task in about ~50ms instead of 800+ ms. The PHP file is hosted by the built in PHP server and acts as a proxy to HFS (the files themselves are still hosted on HFS).

I'm giving up on setting Cache-Control, since I have created a workable solution.

2

HFS ~ HTTP File Server / Re: Controlling the Cache-Control header

« on: August 26, 2017, 06:12:24 PM »

It is because your IP that is accessible to me situates you in Belgium, which could lead me to suppose that you could speak French

For your information, only the lower half of Belgium speaks natively French.

I actually want the content to be ALWAYS cached, no matter what. That's what Cache-Control "Public" is for. I don't see Cache-Control "Public" anywhere after adding it to the template.

I looked at about:cache and it has no entry for that URL. The url I'm using is http://localhost:8080/wallpapers/?tpl=list&folders-filter=\&recursive

3

HFS ~ HTTP File Server / Re: Controlling the Cache-Control header

« on: August 26, 2017, 05:22:22 PM »

I checked that 'public' was present in the answer using HTTPFOX plugin in Firefox, so if your browser does not respond correctly, either it does not fit or it conflicts with another value By default.

I first used Firefox but tried SeaMonkey as well (+HttpFox), putting {.add header|Cache-Control: no-cache, no-store, must-revalidate, max-age=-1, public.} just before </head> three times (three occurences of </head>). It still returns Cache-Control "no-cache, no-store, must-revalidate, max-age=-1".

Reduce the number of values to detect a possible conflict in Cache-Control

What do you mean?

Si je me fie à  google, j'ai bien à faire à une personne en belgique ou utilisant un proxi de ce pays?

<s>I don't know why you're writing to me in French. French is not my native language (Dutch is) and my understanding of and my fluency in the English language is better If you know how to speak Dutch you're welcome to do so.</s> I just read your signature so I understand it now.

I don't understand exactly what you mean by this. I'm not behind a proxy.

4

HFS ~ HTTP File Server / Re: Controlling the Cache-Control header

« on: August 26, 2017, 04:50:58 PM »

Thanks for your reply. I tried adding {.add header|Cache-Control: no-cache, no-store, must-revalidate, max-age=-1, public.} after each </head> but it didn't work, the default Cache-Control value is still used. I also tried {.add header|Cache-Control: Public.} but that didn't work either. I even closed and restarted HFS to no avail.

A workaround (using the older version of HFS) is welcome too, if you know enough details.

5

HFS ~ HTTP File Server / Controlling the Cache-Control header

« on: August 26, 2017, 02:32:40 PM »

Hi. I would like to set Cache-Control to "Public" instead of the default "no-cache, no-store, must-revalidate, max-age=-1".

I tried Other options -> Edit event scripts with this:
[request]
{.add header|Cache-Control: Public.}

But it doesn't work. What did I do wrong?