Postman-echo returns "http" for "x-forwarded-proto"

Help Hub
1

Greetings,

We are experiencing the same issue from Postman echo https echoes as http, we are currently observing “x-forwarded-proto” being returned as “http” instead of expected “https”.

Part of the response that we are getting:

"headers": {
    "host": "postman-echo.com",
    "x-forwarded-proto": "http",
    "x-request-start": "t1733364600.565",
    "connection": "close",
    "content-length": "20",
    "x-forwarded-port": "443"
}

This is causing issues in our CI/CD pipeline. Can you please take a look?

Thanks,
Nikita

2

Hey @material-cosmonaut-4 :wave:t2:

Could you explain more about how you’re using the echo service in your pipeline?

How does that tie into your workflow in your given context?

3

Hey @material-cosmonaut-4 :wave:

This should be fixed now and showing the correct value in the header. :pray:

I’d still love to hear how you’re making use of the Echo service in your context.

4

Hi @danny-dainton,

Thanks for the quick fix, I can confirm that we are now getting “https” value back.

As for the context question - sure! We have a service that uses various custom HTTP clients. These clients need to be tested and the simplest way for us during the time was to use a 3rdparty server, like Postman Echo. So we are testing that those HTTP clients are able to connect, send out requests and get back correct responses - that means that we have very strict tests with response values. These tests are baked into our CI/CD pipeline so that we can catch any issues before we use those clients in production. Hope this answers your question!

Thanks,
Nikita

5

Thanks for the response :trophy:

There is obviously the huge risk of being reliant on a 3rd party API, that you have no control over, to determine if your checks are returning the expected results. :sweat:

Appreciate you using the service but that’s always something to be aware of. :pray: