Optimize Varnish 6 Caching

Job ID: 39921997

Budget: €30 – €250 EUR

I have a dedicated Varnish 6 instance (AlmaLinux) that sits in front of several separate backend web-servers. My goal is to fine-tune the VCL so public HTML is cached reliably while respecting private content rules:

• When the origin response contains no private directives (no Set-Cookie, no Cache-Control: private / no-cache, etc.) and the object is an HTML page, Varnish should cache it for 30 minutes.
• When the origin does send an Expires header, Varnish must honour that value exactly.

Although the foundations are in place, pages that should be cached are still being fetched from the backend. You’ll have access to a staging Varnish box plus three to five real sites; simply point your hosts file to test. We use a pubkey to log in to the varnish server. The /etc/varnish directory will be placed under Git versioncontrol so every VCL change is tracked.

Deliverables
• Updated VCL that achieves the two behaviours above and survives a full service restart
• A brief write-up highlighting what in my current setup prevented proper caching and how your changes resolve it

Please be comfortable debugging Varnish 6 in a live-like environment and working directly on AlmaLinux.
Related categories: Varnish Cache Performance Tuning