duplicate DB cache items

[sdarwin]

This is low priority, but still a curiosity. There seem to be double cache entries in the database with exactly the same content.

cache_key	content_type
static_content_boost_1_89_0/libs/beast/doc/html/beast/quickref.html	text/html; charset=utf-8
static_content_1_89_0/libs/beast/doc/html/beast/quickref.html	text/html; charset=utf-8

what is the reason? Would it cause any problems to "fix"? Or is there a reason to leave as-is.

[sdarwin]

The archive in S3 is named "boost_1_89_0/", so if Django passes the request back to S3 without modification, the website will host a page with a name "boost_1_89_0/" and the corresponding DB cache entry will match.

What if...

At the nginx level, create a redirect:

https://www.boost.org/doc/libs/boost_1_88_0/doc/html/accumulators.html

to

https://www.boost.org/doc/libs/1_88_0/doc/html/accumulators.html

(in a generalized way with a regex, affecting all pages.)

That would prevent the following request from ever reaching Django:

https://www.boost.org/doc/libs/boost_1_88_0/doc/html/accumulators.html

Since it would be redirected at an earlier step.

Then, the problem vanishes automatically. It won't cache "boost_1_88_0" if such a page has 0 visitors, at all times.

[sdarwin]

maybe to repeat unnecessarily, could also use "URL routes", but the issue is not caching at all. it's front-end routing.