Skip to content

StatusCodeChecker should use rules based on regexp URLs instead of paths #18

Open
@cristiingineru

Description

@cristiingineru

The rules of the StatusCodeChecker can be expressed in 4 ways, example:

{
    "code": 200,
    "exceptions": {
        "/": 301,
        "/contact": [
            301,
            302
        ],
        "/product-\d*": {
            "regexp": true,
            "code": 301
        },
        "/item-\d*": {
            "regexp": true,
            "code": [301, 302]
        }
    }
}

Switching to regexp URLs instead of paths will enable writing more precise and clear rules like this:

{
    "code": 200,
    "exceptions": {
        "https://www\.domain\.com/": 301,
        "https://sub1\.domain\.com/": 301,
        "https://sub2\.domain\.com/": 302,
        "https://.*\.domain\.com/product-\d*": 301,
        "https://sub1\.domain\.com/item-\d*": 301,
        "https://sub2\.domain\.com/item-\d*": 302
    }
}

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions