Webhook call to non-www domain | Community
Skip to main content
A
AnkitaVa
New Participant
June 28, 2020
Solved

Webhook call to non-www domain

  • June 28, 2020
  • 2 replies
  • 2560 views

Hi

 

I am configuring a webhook with method type as POST for the below URL's

production: https://www.example.com  

UAT: https://www-uat.example.com  

 

For the prod URL, it is working fine in webhook as well as through POSTMAN

but for the UAT url, it is working fine in POSTMAN but throwing error string as "www-uat.example.com Name or service not known" and no status code

 

Has anyone encountered this kind of issue before? Any suggestions here please to get this resolved?

 

Thanks.

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by SanfordWhiteman

If you're behind a corporate firewall (including a VPN) when using Postman, the UAT hostname (www-uat.example.com) may only resolve when using your company's private DNS server, but not when using the public DNS infrastructure used by everybody else.

 

If the hostname isn't public, the UAT webserver may still be available publicly. If it's available publicly, you'll be able to connect to it using its IP address and a manual Host: header in Marketo.

 

Other than that, you should look at the Postman HTTP headers to see if you have some authorization headers that you forgot about.

2 replies

SanfordWhiteman
SanfordWhitemanAccepted solution
New Participant
June 28, 2020

If you're behind a corporate firewall (including a VPN) when using Postman, the UAT hostname (www-uat.example.com) may only resolve when using your company's private DNS server, but not when using the public DNS infrastructure used by everybody else.

 

If the hostname isn't public, the UAT webserver may still be available publicly. If it's available publicly, you'll be able to connect to it using its IP address and a manual Host: header in Marketo.

 

Other than that, you should look at the Postman HTTP headers to see if you have some authorization headers that you forgot about.

A
AnkitaVaAuthor
New Participant
July 6, 2020

Hi Sanford,

 

The HTTP Headers were correct, the issue was around VPN.

Thanks for helping out.

Oz_Platero
Oz_Platero
New Participant
June 28, 2020

Hello @ankitava ,

 

Do you have actual URLs we can look at?

 

The UAT just looks like a different type of setup for a CNAME.

Terms & ConditionsAccessibility statement

Loading footer...