Our use case - MkDocs Material (with mkdocs-redirect) generates "soft redirects". - 200 OK response with the redirect done using http-equiv.

Example:

$ curl -i https://doc.ibexa.co/projects/userguide/en/5.0/pim/pim/ 

<!doctype html>
<html lang="en">
<head>
    <meta charset="utf-8">
    <title>Redirecting...</title>
    <link rel="canonical" href="../../product_catalog/product_catalog/">
    <script>var anchor=window.location.hash.substr(1);location.href="../../product_catalog/product_catalog/"+(anchor?"#"+anchor:"")</script>
    <meta http-equiv="refresh" content="0; url=../../product_catalog/product_catalog/">
<script async type="text/javascript" src="/_/static/javascript/readthedocs-addons.js"></script><meta name="readthedocs-project-slug" content="ez-systems-user-documentation" /><meta name="readthedocs-version-slug" content="5.0" /><meta name="readthedocs-resolver-filename" content="/pim/pim/" /><meta name="readthedocs-http-status" content="200" /></head>
<body>
You're being redirected to a <a href="../../product_catalog/product_catalog/">new destination</a>.
</body>
</html>

So yes, checking for the URL property sounds reasonable.

Uh oh!

Soft redirect #2154

Description

Metadata

Metadata

Assignees

Labels

Type

Fields

Projects

Milestone

Relationships

Development

Issue actions