Matt Westcott

Sounds like a lot of over-engineering to me... can we not use Django's existing cache framework here? https://docs.djangoproject.com/en/4.1/topics/cache/

@ababic OK. I'm strongly against replacing something simple that works consistently (albeit not as quickly as we'd like) with something where the developer has to get their head around new...

Setting the correct port under Settings -> Sites should fix this too. Generally we aim to avoid referencing hostnames and ports in our URL routing / construction logic, and keep...

@GeekGawd I don't have capacity to provide mentoring support at this time, sorry. In the description above I've given a detailed breakdown of the steps required - in particular, the...

@GeekGawd Thanks for looking into this! I can replicate the behaviour you describe, but I think this is the fault of the Cache-Control header, not the Etag logic: on the...

Completed in #9820.

Completed via #9860. @Ananjan-R I've [added you to the contributors list](https://github.com/wagtail/wagtail/commit/992d4c4ecbe54280d1e764d25ad2784e5691a1ef) as "Ananjan-R" - please let me know if you'd like that name updating to anything else.

@vsalvino Does this mean it would be reasonable to close this issue? Or are we looking at implementing a workaround on the Wagtail side as well as addressing it in...

Just to note that the use of `Cast` in wagtail/search/models.py has been there since 2.15 - so if `Cast` in itself is a problem, then this potentially spans more than...

I'm not really sold on the `` tag approach - it feels like it could get very verbose if this gets widely adopted and we end up outputting dozens of...