Postman echo https echoes as http

🙋 Help
1

I am not sure this is the correct place to ask the question so please redirect me to the right place if this is the wrong place for this question.

When using tests to post data to postman echo at https://postman-echo.com/get , the response coming back has changed over the last few days. In the past it used to be

{
  "args": {
    "testGetQuery": "test"
  },
  "headers": {
    "x-forwarded-proto": "https",
    "x-forwarded-port": "443",
    "host": "postman-echo.com",
    "accept-encoding": "gzip, deflate",
  },
  "url": "https://postman-echo.com/get?testGetQuery=test"
}

and now it has changed to

{
  "args": {
    "testGetQuery": "test"
  },
  "headers": {
    "host": "postman-echo.com",
    "x-forwarded-proto": "http",
    "x-request-start": "t=1718178185.406",
    "connection": "close",
    "x-forwarded-port": "443",
    "accept-encoding": "gzip, deflate",
  },
  "url": "http://postman-echo.com/get?testGetQuery=test"
}

notice that the url has changed to http and it looks like my request is passing through some load balancer that uses http to the backend and adds the x-forwarded-proto header as well.

Is this a planned change or a bug? should I adapt my tests to these new responses or if this is a bug wait for it to be fixed?

2

The following is using the web client, but seems to be returning as you would expect.

{
    "args": {
        "testGetQuery": "test"
    },
    "headers": {
        "host": "postman-echo.com",
        "x-request-start": "t=1718210739.657",
        "connection": "close",
        "x-forwarded-proto": "https",
        "x-forwarded-port": "443",
        "x-amzn-trace-id": "Root=1-6669d0b3-1b01055d4ffd924d2046b2d2",
        "accept-language": "en-GB,en;q=0.9,en-US;q=0.8",
        "user-agent": "PostmanRuntime/7.39.0",
        "accept": "*/*",
        "cache-control": "no-cache",
        "postman-token": "e446141d-e8eb-4c2f-909a-7d083c0ba5c3",
        "accept-encoding": "gzip, deflate, br",
        "cookie": "sails.sid=s%3A8aPJW-DfLgUaizU1_-vzn_-NmQ8h5BC-.MgKQ5lk6FHMCtMC2AoBgFNzqDqYWYuAyjHD%2BnIkDsEk"
    },
    "url": "https://postman-echo.com/get?testGetQuery=test"
}
3

Hey @DanAvni,

It was a bug introduced due to a recent infrastructure change, but it has been fixed now.

Let us know if the issue persists.

1 Like
4

This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.