(chore): ajax cache to reduce server load

[ndbiaw]

normal, ajax will add timestamp at the end of request. this config remove it

[Difegue]

👋 Wouldn't this lead to users not getting up-to-date data when they modify metadata for their archives, which changes the internal indexes/the result of the search API call?

There's already serverside cache for searches, so I don't think this would be very useful 🤔

[ndbiaw]

👋 Wouldn't this lead to users not getting up-to-date data when they modify metadata for their archives, which changes the internal indexes/the result of the search API call?

cache: true doesn't actually change anything, cache: false just adds a timestamp at the end of the URL to prevent content from being cached if the appropriate header is present. User can still get up-to-date results, this only helps if the user uses the header to set the cache but ajax always adds timestamp to the end of the URL so making browser cache useless. This is useful for reducing the request to the server.

There's already serverside cache for searches, so I don't think this would be very useful 🤔

This change reducing the request to the server if the user sets the appropriate header, so I don't think server-side caching is really relevant, because if the request is cached it won't make the request to the server.

[Difegue]

Thanks for the explanation - Don't see anything wrong with merging this in that case. Thanks!

[holopin-bot]

Congratulations @ndbiaw, you just earned a holobyte! Here it is: https://holopin.io/holobyte/clo4jpati130420flb5ayoq2sn

This badge can only be claimed by you, so make sure that your GitHub account is linked to your Holopin account. You can manage those preferences here: https://holopin.io/account.
Or if you're new to Holopin, you can simply sign up with GitHub, which will do the trick!