Re: svn commit: r1936555 - in subversion/site/staging: . blog docs docs/community-guide docs/release-notes pronunciation security style
Nathan Hartman <[email protected]> Wed, 29 Jul 2026 14:13:38 -0400
| Newsgroups | gmane.comp.version-control.subversion.devel |
|---|---|
| Message-ID | <CAJT2EHpPuCisTn01EjK+njHdEBpzBWjOYANLaEwoajVTSwPb=Q@mail.gmail.com> |
On Wed, Jul 29, 2026 at 9:46=E2=80=AFAM Branko =C4=8Cibej <[email protected]= > wrote: (snip long earlier quoted text) > Changing this in the source code just smells wrong to me. I had a quick l= ook and it appears that none of the HTML responses from apache.org have any= cache control headers set. However, the response for our 'style/site.css' = does have both ETag and Last-Modified (about 3 hours ago on the main site, = apparently). Still, since there's no Cache-Control max_age or similar, any = browser can decide to cache the page as long as it likes. > > The correct way to fix this is to set cache-control headers appropriately= , but this should be done by Infra, not us. > > -- Brane This sounds like the correct solution to me. I'm happy to ask Infra; what max age should we ask for? Is there some customary value for this? Thanks, Nathan