Possibility to use lokal settings

[Woribe]

Im using Verify.Http for my integrationtests using the webapplicationfactory framework.
Im building a fetered authentication application that uses jwt's.
Some of the endpoints relais heavly on headers and some less.

For example my login-endpoint sets a httponly jwt.
So I would like to have my test verify that the responsemessage contains headers like this, where the response headers clealy contains a "Set-Cookie":

{
  Version: 1.1,
  Content: {
    Headers: [
      {
        Content-Type: [
          application/json; charset=utf-8
        ]
      }
    ]
  },
  StatusCode: OK,
  ReasonPhrase: OK,
  Headers: [
    {
      Set-Cookie: [
        jwt=REDACTED
      ]
    }
  ],
  TrailingHeaders: [],
  RequestMessage: {
    Version: 1.1,
    Content: {
      Headers: [
        {
          Content-Type: [
            application/json; charset=utf-8
          ]
        },
        {
          Content-Length: [
            59
          ]
        }
      ]
    },
    Method: {
      Method: POST
    },
    RequestUri: http://localhost/api/Authentication/Login,
    Headers: []
  },
  IsSuccessStatusCode: true
}

When im doing VerifyHttp.Initialize(); some converters is set on the global VerifierSettings which simplifies the headers.
This means that when im trying to verify the response of my login endpoint, im left with a response that looks like this:

{
  "Version": "1.1",
  "Status": "200 OK",
  "Cookies": {
    "jwt": "REDACTED"
  },
  "RequestMessage": {
    "Method": "POST",
    "Uri": "http://localhost/api/Authentication/login",
    "Content": {
      "Headers": {
        "Content-Length": "59",
        "Content-Type": "application/json; charset=utf-8"
      },
      "Value": ""
    }
  }
}

Some of my tests is okay with the simplyfied headers, but this means that i need a way to specify the simplicity of the headers.
So i wondering if it would be possibly to somehow specify how simple the headers should be?

And a side note.. it is pretty hard to use ScrubLinesWithReplace after VerifyHttp.Initialize();.
I havent found a way to scrub the jwt, without ignoring the entire header.

Kind regards

[SimonCropp]

can you submit a PR with a failing test that shows your desired expected verified file

[Woribe]

Hmm.. don't know if that would help.
I might be doing somethin wrong since my headers is so simplified.
I want a result that is more or less like this from your documentation: https://github.com/VerifyTests/Verify.Http?tab=readme-ov-file#resulting-verified-file-1

But they way that i have tried to setup my testsuite i get somthing like this:

{
  "Version": "1.1",
  "Status": "200 OK",
  "Cookies": {
    "jwt": "REDACTED"
  },
  "RequestMessage": {
    "Method": "POST",
    "Uri": "http://localhost/api/Authentication/login",
    "Content": {
      "Headers": {
        "Content-Length": "59",
        "Content-Type": "application/json; charset=utf-8"
      },
      "Value": ""
    }
  }
}

The headers is gone..

Im using a webapplicationfactory to create a httpclient.
And im having a hard time injecting the recording globally as in you documentation: https://github.com/VerifyTests/Verify.Http?tab=readme-ov-file#add-globally
The AddRecordingHttpClient(); method extends on a ServiceCollection instead of a IServiceCollection.

[SimonCropp]

sorry if you cant distill this down to a minimal repro that illustrates the problem, i dont think i can help