Css/js resources should be cached in browser

[kelson42]

proper Http response header should be set

[yashikajotwani12]

Hey @kelson42 , please assign me this issue, I would start building this soon, I want to be a part of Gsoc'2021 . This could be a good start for me.

[kelson42]

@yashikajotwani12 What do you propose to do to fix this issue?

[abdulmoiz37]

Hello @kelson42,I would Like to Contribute to this issue so that i can Submit a Proposal to GSOC through Kiwix.org.Can i Work on this or Is Someone Else working Currently?

[kelson42]

@abdulmoiz37 You can work on this. Better explain here first how you plan to fix the problem.

[jahnavi0625]

Hey is the issue resolved? I would love to contribute

[audiodude]

@jahnavi0625 see responses above. How do you plan to solve it?

[its-me-maady]

Can you explain the issue in detail pls @kelson42

[audiodude]

I can explain it. Basically, we want our CSS and JS assets to be served from the nginx proxy Docker image with the Cahe-Control headers set appropriately.

[benoit74]

You can even get inspiration from https://github.com/openzim/zimfarm/pull/1537/changes (might need to be adapted to WP1 context obviously)

[its-me-maady]

Hi @audiodude and @benoit74 , I'd like to work on this. My plan: create a cache.conf file in docker/frontend/ with Cache-Control: public, max-age=31536000, immutable and expires 1y for .css and .js assets, following the same pattern as gzip.conf. Add it to the Dockerfile alongside the existing gzip config. Will open a PR shortly.