Tom Akehurst

I'd be reluctant to change the semantics of the existing flag as that would be a breaking change for a lot of projects. The documentation is clearly wrong, so that...

Similar to #1407

Hmmm....I'm dubious about either breaking backwards compatibility or adding configuration complexity for a niche case like this, particularly since there's a workaround.

Have you tried setting a higher header buffer size per these docs? https://wiremock.org/docs/configuration/#jetty-configuration

Setting the request header size to 64kb worked OK for me. Are you sure (given that you're using WireMock indirectly via Spring) that you're actually setting the config value in...

Those are not the correct parameters for setting header size in WireMock. I suggest setting the ones documented here: https://wiremock.org/docs/configuration/#jetty-configuration WireMock hasn't changed in any way between those versions regarding...

This class doesn't currently have an equals method as within WireMock it's never used in a way that requires it. In what context do you find the lack of an...

OK, I think it makes sense to support that use case, so I'll tag this as an enhancement. Happy to receive a PR if you feel like creating one.

You could use `{{#assign 'decoded'}}{{base64 ... }}{{/assign}}` then pass the `decoded` variable to `{{regexExtract}}`

I wouldn't describe it as a bug exactly, since I assume you're still getting the correct result. Unless that's not the case? Definitely not optimal from a performance PoV though....