On 5/01/20 7:24 am, Andrei Pozolotin wrote:
> Amos, hello:
>
> On 2020-01-04 05:14, Amos Jeffries wrote:
>> Expires header is an HTTP/1.0 protocol feature. Its absence has no
>> meaning.
>> The 302 response is explicitly defined in HTTP as a *temporary* object
>> which can change at any time. The
Amos, hello:
On 2020-01-04 05:14, Amos Jeffries wrote:
Expires header is an HTTP/1.0 protocol feature. Its absence has no
meaning.
The 302 response is explicitly defined in HTTP as a *temporary* object
which can change at any time. The *presence* of Cache-Control:max-age
or
Expires set a mini
On 4/01/20 11:49 pm, Andrei Pozolotin wrote:
> Alex:
>
> On 2020-01-03 14:19, Alex Rousskov wrote:
>>> Question: how can one force the caching of 302 responses
>>> without the Expires header and with Strict-Transport-Security max-age
>>> header?
>>
>>
>> You can modify Squid to handle Strict-Trans
Alex:
On 2020-01-03 14:19, Alex Rousskov wrote:
Question: how can one force the caching of 302 responses
without the Expires header and with Strict-Transport-Security max-age
header?
You can modify Squid to handle Strict-Transport-Security specially or
you can write an ICAP or eCAP service t
