Hi,

 

 

I'm not so familiar with the HTTPCaller, but I have a success experience.

 

In my case, the posting values were HTML form inputs and did set the transformer parameters like this.

 

Upload Data: Multipart / Form Data

 

Multiple Upload:

 

Name  |  Type  |  Value

 

mail_address  |  StringUpload  |  xxxx@yyyy.com

 

indutry_code  |  StringUpload  |  1

 

etc.

 

 

By a case, you may have to access to the form page to get a Cookie by an HTTPCaller with GET method and then issue the POST request with another HTTPCaller.

 

In such a case, set "Yes" to the "HTTP Client Options / Save Cookie" parameter of the two HTTPCallers.

 

 

Hope this helps.

 

 

Takashi

---

Thanks Tashi for responding:

 

 

I’ve had a feeling I’ve been real close but myself and coworker spent quite of bit of time on this one.

 

I liked your form idea and using two httpcallers - as this service has a test form that use a post method. 

 

 

But the was solution much simpler in my case – I’m still a FME Newbie and had to remember I could enter a value

 

“Content-Type: application/x-www-form-urlencoded”

 

 

 

BTW can you use a tool like fiddler - to see if I could monitor my network request that is a bit more descriptive than in the FME log file?

 

 

Thanks Again:

 

Ian

 

 

---

Here is a workspace that uses POST and also standardizes addresses by way of geocoding against an Esri geocoder service (not public).batchgeocode.fmw

---