Any recent changes to 'Host' request header?

🙋 Help
, ,
1

Currently using Postman For Windows
Version: 11.12.0
UI version: 11.12.0-ui-240903-1253
Desktop platform version: 11.12.0
Architecture: x64
OS platform: win32 10.0.22631

Back in May, I was able to test our API server running in Azure with a URL like this:

https://example.com:443/api/1/widgets

I made additions to our API last Friday (September 13th!) and now our firewall is blocking the requests, which according to our firewall admins, is likely because the ‘Host’ header includes the port number:

Host: “example.com:443”

If we remove the port number, everything works as expected:
https://example.com/api/1/widgets
Host: “example.com”
Firewall is happy and API server receives and responds to the request.

I would like to know if there have been any changes in Postman since May that would affect how the Host header is populated, or anything else that might be helpful in troubleshooting this.

Of course, it may also be a configuration issue in our firewall, but wanted to check on the Postman side just for completeness.

Thanks

2

Hey @stdenisg :wave:

Welcome to the Postman Community! :postman:

No changes that I have seen or I’m aware about.

3

Thanks for your help!

Hopefully we’ll find some clue elsewhere that will explain the new behavior we’re observing now.

Cheers

4

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