Thanks Dridi and Guillaume for clarification!
On Thu, Jun 15, 2023, 18:30 Guillaume Quintard
wrote:
> Adding to what Dridi said, and just to be clear: the "cleaning" of those
> well-known headers only occurs when the req object is copied into a beteq,
> so there's nothing preventing you from sta
Adding to what Dridi said, and just to be clear: the "cleaning" of those
well-known headers only occurs when the req object is copied into a beteq,
so there's nothing preventing you from stashing the "cache-control" header
into "x-cache-control" during vcl_recv, and then copying it back to
"cache-c
On Thu, Jun 15, 2023 at 9:33 AM Uday Kumar wrote:
>
>
>> There is this in the code:
>>
>> > H("Cache-Control", H_Cache_Control, F ) // 2616
>> > 14.9
>>
>> We remove the this header when we create a normal fetch task, hence
>> the F flag. There's a reference to RFC2616 sec
> There is this in the code:
>
> * > H("Cache-Control", H_Cache_Control, F ) *//
> 2616 14.9
>
> We remove the this header when we create a normal fetch task, hence
> the F flag. There's a reference to RFC2616 section 14.9, but this RFC
> has been updated by newer documents.
On Wed, Jun 14, 2023 at 9:02 AM Uday Kumar wrote:
>
> Hi Guillaume,
>
> Thanks for the response.
>
> Can you provide us with a log of the transaction please?
>
> I have sent a Request to VARNISH which Contains Cache-Control: no-cache
> header, we have made sure the request with cache-control head
Hi Guillaume,
Thanks for the response.
Can you provide us with a log of the transaction please?
I have sent a R*equest *to VARNISH which Contains *Cache-Control: no-cache
header*, we have made sure the request with *cache-control header* is a
MISS with a check in *vcl_recv subroutine*, so it's a
Hi Uday,
Can you provide us with a log of the transaction please? You can run this
on the Varnish server:
varnishlog -g request -q 'ReqHeader:Cache-Control'
And you should see something as soon as you send a request with that header
to Varnish. Note that we need the backend part of the trans
Hello,
When a user refreshes(F5) or performs a hard refresh(ctrl+F5) in their
browser, the browser includes the *Cache-Control: no-cache* header in the
request.
However, in our* production Varnish setup*, we have implemented a check
that treats* requests with Cache-Control: no-cache as cache misse
