chilly-arm-43055
05/19/2022, 8:39 AM"url": "<*>"
) but I get a 404 error stating no rule matched the request.
[
{
"id": "default-passthrough",
"match": {
"url": "<*>",
"methods": [
"DELETE",
"GET",
"HEAD",
"PATCH",
"POST",
"PUT"
]
},
"upstream": {
"url": "<http://127.0.0.1:8080/>"
},
// Authenticators, Authorizers, Mutators, etc.
}
]
How would you do such a rule?happy-morning-85531
05/19/2022, 8:43 AM<.*>
I have it working with
match:
url: "https://<.*>.<http://dev.example.com|dev.example.com><.*>"
chilly-arm-43055
05/19/2022, 9:19 AM<*>
(glob pattern matching) doesn’t work but <.*>
(regexp matching) does work.
cc @swift-chef-97535
Thank you guys!happy-morning-85531
05/19/2022, 9:56 AM#
access_rules:
## Matching strategy ##
#
# This an optional field describing matching strategy. Currently supported values are 'glob' and 'regexp'.
#
# Default value: regexp
#
# One of:
# - glob
# - regexp
#
# Examples:
# - glob
#
# Set this value using environment variables on
# - Linux/macOS:
# $ export ACCESS_RULES_MATCHING_STRATEGY=<value>
# - Windows Command Line (CMD):
# > set ACCESS_RULES_MATCHING_STRATEGY=<value>
#
matching_strategy: glob
As you see, the default is regexpchilly-arm-43055
05/19/2022, 9:57 AMglob
in my config, but still <*>
wasn’t workingswift-chef-97535
05/19/2022, 11:51 AMchilly-arm-43055
05/19/2022, 11:53 AM<.*>
works as expected, I ended up with http<s?>://<.*>
to be a bit more specific