I'm running into an issue with trying to mock an endpoint that I can't figure out what is happening. I'm attempting to use a simple url, method, header match on the request, and when I submit the request, it says it doesn't match seemingly based on the header Real Request

POST /v1/token HTTP/1.1
Host: localhost:54287
traceparent: oa-2a7ac95c456e05294be1ff5e58083ee8-kaldfjl
Content-Type: application/json
Content-Length: 22

{
    "test": true
}

Mapping - only included a portion that was relevant

"request": {
                "url": "/v1/token",
                "method": "POST",
                "headers": {
                    "traceparent": {
                        "contains": "2a7ac95c456e05294be1ff5e58083ee8"
                    }
                }
            }

I'm checking the various endpoints to diagnose like the near misses endpoints, but I can't see any revelant information as to why it wouldn't match. Is there any other things I can check like adding better logging in the docker container that wiremock is running inside?

pretty hard to diagnose without all the information. if you can create a repo that reproduces the problem i can take a look

I discovered the docker

WIREMOCK_OPTIONS: '--verbose'

to enable more logs

Did you get anything that helped in the verbose logs?

I don't believe so. I do have the near misses call that returns data, but I can't see anything that stands out with it. The odd thing is that I had previously gotten this to work with seemingly the exact same call. The only thing I'm doing differently is using the Wiremock.Org.Abstractions library that is tied to Wiremock.Net and manually creating my own client methods to post to the admin endpoints to create the mappings

Ah, I am not a .Net dev unfortunately. I wonder if you can get this working in WireMock standalone to see if we can isolate the problem a little. Other than that, providing an example app might be useful like already mentioned or posting in the #C059E0MBM29 channel might be a good idea

Thank you, I didn't realize that channel existed, I will post there

Not sure what that is either. That must be something specific to the .Net library

It's in the base API as well, but I think the .net library is always passing it instead of only passing it when its set

Ah, yes so it is. I haven't seen that before. Will have to investigate that further

I'll make a note on the .net library that has this issue and potentially have them have fields that aren't required to be nullable.

Awesome. Glad you worked it out in the end