Is path completely matched or just the beginning in "ignored"?

1 
"ignored": [
    {
        "path": "/v1/ignored/literal",
        "method_actions": {
            "GET": {
                "action": "no_action",
                "code": 200,
                "data": "",
                "headers": {}
            }
        }
    }
]

If I get a call to /v1/ignored/literal/something will this be ignored too? Does the path have to match completely?

2

The match is strict, if you want to introduce variability, you can use wildcards.

Wildcards take the form of curly braces, such as:

"/v1/ignored/{wildcard}"

Anything in curly braces is transformed into a wide regex matching group:

(.*)

It doesn’t get captured, but it means you can ignore resource IDs etc.

3

Hi @Martin,
I also have a problem with the ignore function.

These are the logs:
msg=“Attempted access with malformed header, no auth header found.” path="/myservice/Image/SW1hZ2VzL2pwZ19sYXJnZS8xMGNlZjczZC0yNWJjLTExZTUtODBjZi0wMDUwNTZiMzE3NzQ="
msg=“request error: Authorization field missing” path="/myservice/Image/SW1hZ2VzL2pwZ19sYXJnZS8xMGNlZjczZC0yNWJjLTExZTUtODBjZi0wMDUwNTZiMzE3NzQ="

And this is part of my definition:
{
“name”: “myservice”,
“slug”: “myservice”,
“auth”: {
“auth_header_name”: “X-TTS-ApiKey”
},
“version_data”: {
“not_versioned”: true,
“versions”: {
“Default”: {
“name”: “Default”,
“expires”: “”,
“paths”: {
“ignored”: [],
“white_list”: [],
“black_list”: []
},
“use_extended_paths”: true,
“extended_paths”: {
“ignored”: [
{
“path”: “/myservice/Image/{any}”,
“method_actions”: {
“GET”: {
“action”: “no_action”,
“code”: 200,
“data”: “”,
“headers”: {}
}
}
},
{
“path”: “/Image/{any}”,
“method_actions”: {
“GET”: {
“action”: “no_action”,
“code”: 200,
“data”: “”,
“headers”: {}
}
}
}
]
},
}
}
},
“proxy”: {
“preserve_host_header”: true,
“listen_path”: “/myservice/”,
“strip_listen_path”: false
}

I’m not sure if I do not strip the listen path, if I need the /myservice or not and if I need that / at all.

4

If stripping the listen path (i.e. removing it fromthe request that goes to your upstream), you do not need to include it in the path match.

The ignore, black and white lists are all case insensitive, it’s recommended to enter the path in lowercase in the designer / definition because the gateway will check the lowercase version of the request URL, this only applies . to these middleware though, the other middlewares are case sensitive.