- Issue created by @todea
- π¨πSwitzerland berdir Switzerland
redirect needs to check every request, it makes sense that most don't exist. The proposed caching might help that you already linked to depending on the path that this involves.
I don't know why it quits afterwards, but I assume you might be using dynamic page cache and those requests might involve different query strings or something that are a dynamic page cache hit or a 404 page or something then.
the example here seems to be a link to an asset file, that should only be requested once and then exist on the file system.
Nothing unexpected here in regards to redirect.
- πΊπΈUnited States todea
the example here seems to be a link to an asset file, that should only be requested once and then exist on the file system.
That's what I was wondering. We have constant requests like this for our aggregated CSS & JS hitting the database.
We do have dynamic page cache enabled. However, we can try disabling it since the majority of our site is static.
- π¨πSwitzerland berdir Switzerland
> We do have dynamic page cache enabled. However, we can try disabling it since the majority of our site is static.
That's not my point at all. Nothing wrong with redirect, nothing wrong with Dynamic page cache.
If it's specifically asset requests that are happening, make sure that those files actually exist on the filesystem afterwards. The idea is that the first request hits Drupal and all following requests are static files. That URL looks unusual, by default it's sites/default/files/assets. Make sure that folder is writable and Drupal puts them in the right place, check your asset stream wrapper configuration.
Automatically closed - issue fixed for 2 weeks with no activity.