remove global browser caching

[anoymouserver]

API calls for the frontend get stuck in the browser cache and the Apache .htaccess also doesn't contain anything similar.
Fixes#5472

[MorrisJobke]

See #2197 (comment)

cc @jivanpal@josh4trunks

[josh4trunks]

@jivanpal it looks like this was added back in summer 2020. I also do not see any default max-age in the .htaccess. Please confirm if there is any specific reason you want to keep it, otherwise I agree with @anoymouserver that we should remove it.

[jivanpal]

@josh4trunks, I used expires 1m as a default for the current config just because it's generally good practice to cache things, but if this is affecting functionality, then of course please change it; I am not familiar enough with the inner workings of Nextcloud to really be able to provide any more info than I already have in the comments on the config, so I am happy for you to make any changes to it. The intent was always just to create something semantically equivalent to the Apache config, but in a concise, readable, efficient way for Nginx admins.

Also, from #2197, I said:

Regarding the specific issue with Cache-Control headers there, do you know if Nginx overrides HTTP headers set by PHP? If so, we probably do need to get rid of the expires mentioned by @anoymouserver and instead rely on PHP to set the header, or do some sort of if on $http_cache_control.

If expires 1m is never of any real benefit, then I would suggest just getting rid of it.

[josh4trunks]

I'm not using a default expires in my config, so maybe why I never noticed any issues.
👍

[MorrisJobke]

/backport to stable20

[MorrisJobke]

/backport to stable19

[MorrisJobke]

/backport to stable18

[backportbot-nextcloud]

The backport to stable19 failed. Please do this backport manually.

[backportbot-nextcloud]

The backport to stable18 failed. Please do this backport manually.