Skip to main content
Archived

HTTPCaller improvements

Related products:FME Form
  • April 28, 2017
  • 1 reply
  • 19 views

fmelizard
Safer
Forum|alt.badge.img+22

In the HTTPCaller we can specify some settings that will be represented as a Header of the request. For example the Content-Type parameter specified in the Body section sets the Content-Type header of the call. This is not very obvious to see as you can still specify a Content-Type Header in the Header section. Often, if two different Content-Type Headers are set the request may fail, because they compete. The Authentication option also sets Headers behind the scenes.

The Query Parameters show a similar behavior. If we set a Query Parameter it will be added to the end of the request URL behind the scenes. But if this parameter is already part of the URL both will compete.

It would be nice if the Headers and the Query String would be updated on the fly when the URL or a parameter (Body, Authentication) is modified/added and vice versa. The Postman REST API Client is a nice example for this functionality.

This post is closed to further activity.
It may be an old question, an answered question, an implemented idea, or a notification-only post.
Please check post dates before relying on any information in a question or answer.
For follow-up or related questions, please post a new question or idea.
If there is a genuine update to be made, please contact us and request that the post is reopened.

1 reply

fmelizard
Safer
Forum|alt.badge.img+22
  • Author
  • Safer
  • April 28, 2017

I had a situation where in the Headers I specified Content-Type = 'text/xml' However, under the Body section for Content-Type, the drop-down does not contain 'text/xml' as an option so I was always choosing 'Text (text/plain)' or 'XML (application/xml)'. It was not obvious right away that as a user I can specify the Content Type under the Body section manually. At first it seemed as if whatever the drop-down had were the only possible options. So after typing in 'text/xml' manually for Content Type under Body and removing it from the Headers section it worked fine. This improvement can help in avoiding such problems.