As title implies, this regards redirects. When you rename a page for example, it will by default "leave" a redirect on the old slug/path behind. I'm 100% that requests to the Content Delivery API, previously during our development, returned these redirects when querying the API for the "item" with the old slug/path. We would receive 30x headers in the HTTP response. However now we only receive 404's instead. Tried both v1 and v2 of the API. Any idea what could've happened? Regression?