We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
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 } }
The text was updated successfully, but these errors were encountered:
No branches or pull requests
The rules of the StatusCodeChecker can be expressed in 4 ways, example:
Switching to regexp URLs instead of paths will enable writing more precise and clear rules like this:
The text was updated successfully, but these errors were encountered: