Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Open
cristiingineru opened this issue Mar 9, 2023 · 0 comments

Comments

@cristiingineru
Copy link
Collaborator

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
    }
}
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant