403 forbidden when using proxy wiremock in c# unit test

[fl0l-gouze]

Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]

I’ve created an unit test using wiremocknet. I’ve setup so that instead of targeting https://mycompany/private/ it instead target http://localhost:8080/ that forward it then to the https://myco mpany/private

By using Wiremockserver.Start and setting a Logger and an proxyAndRecordSettings.

The issue is that I always have 403 forbidden.
I know that the forward work otherwise I would have no response.
I know the header with authentication are correctly feeded to my http client as I have only switch the url.

By using postman I can see my header correctly fed (if I’m not mistaken)

But it seems wiremock net jinx my auth
Describe the solution you'd like
A clear and concise description of what you want to happen.

Correct forward of header for auth when calling api in forward and record mode

Describe alternatives you've considered
Installed wiremock Java locally to do the forward and record and it worked

Is your feature request supported by WireMock (java version)? Please provide details.
Wiremock Java locally works but I want the net version to be able to have an unit test that record all call to external api so that after record all call are mocked and stored

Additional context
Add any other context or screenshots about the feature request here.

[fl0l-gouze]

For information, the auth information are passed through to my http client by :
Httpclient.DefaultRequestHeaders.Authorization = new AuthentificationHeaderValue(« Basic », Convert.ToBase64String(Encoding.ASCII.GetBytes($«{username}:{password} »)));

I feed both of theses value through
WebProxySettings = new WebProxySettings() {. Username = username, Password = password }

[fl0l-gouze]

I managed to fix my issue, it’s indeed a « shortcoming » of wiremock.net when forwarding a http call to a https call over proxy.

Natively, wiremock Java set up the proxy prefix. This is not the case on wiremock.net
You need to either twist your url construction or set correctly the proxy prefix into the header (took the first option as quick fix only impacting test code)

Will enhance issue and problem but this is a real feature for me.

[StefH]

@fl0l-gouze
Can you please provide clear explanation of what is happening and what should happen?
Provide example project if possible.

[StefH]

@fl0l-gouze
Can you please provide clear explanation of what is happening and what should happen?
Provide example project if possible.