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”.
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!
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.
Appreciate you using the service but that’s always something to be aware of.