Skip to main content
Question

HTTPCaller Enverus API v3 custom header parameter ignored in Form but works in Postman


rzickuhr
Participant
Forum|alt.badge.img+2

Enverus’s Developer API has a custom header option to change the location of next link from the header to the body. When I put X-Omit-Header-Next-Links in the header of Postman I get the expected response: 

Results from Postman
​​​​​

putting X-Omit-Header-Next-Links in the header of HTTPCaller seems to be ignored as no next link is in the response body and the link remains in the response headers.

HTTP Caller with X-Omit-Header-Next-Links
Bottom of response body in Form
Returned API header attributes in Form
​​​​​

Am I doing something wrong or has anyone experienced this behavior?

Thanks in advance,

Randy

3 replies

hkingsbury
Celebrity
Forum|alt.badge.img+54
  • Celebrity
  • May 21, 2024

Do you need to pass a value through for the header? FME might be dropping it as it doesn’t have a value. Try with a <space>?


rzickuhr
Participant
Forum|alt.badge.img+2
  • Author
  • Participant
  • May 21, 2024

Thanks, good thought, I suspected the same thing and tried a space, single and double quotes none of which worked. There doesn’t seem to be a way to inspect what is being sent by HTTPCaller from within Form. Perhaps I need to use something like Wireshark to inspect what is being sent?


hkingsbury
Celebrity
Forum|alt.badge.img+54
  • Celebrity
  • May 22, 2024

I’ll often use Fiddler to verify outgoing calls from Form. Wireshark should also work.

Its definently a valid approach, then you can compare the succesfull call from postman and the one from Flow.

I have noticed in the past that the library that FME uses to send requests adds some of its own headers. In the ‘worst’ case this caused the API i was calling to reject my requests as on of the headers identified it as coming from a python library and the API blocked it as it treated it as a web scraper!

 


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings