This message was deleted.

Hi @Jackie chen this is actually already supported. When you trigger recording via WireMock’s API you can specify a set of parameters to customise the recording including

captureHeaders

. See this bit of the docs for details: https://wiremock.org/docs/record-playback/#customising-your-recordings

@Tom i meant the recording of the whole request headers from the consuming apps without specifying a set of static headers to record.. then we can filter unwanted headers for request matching later

I'm curious why you'd want to do that? Capturing all the headers means you're likely to end up with stubs that are overly strict and don't match the requests you want them to. And although you're planning to filter them afterwards this seems like a lot more work than picking the ones you wanted in the first place.