Skip to main content
Question

HTTPcaller multipart/form-data encoding

  • February 23, 2019
  • 4 replies
  • 113 views

jatoxa
Contributor
Forum|alt.badge.img+12

Hi,

 

 

I'm using HTTPCaller to upload files to an online project management system.

 

It all works great but the file names containing "öäå" are substituted with strange looking "?" symbols.

 

Everything seems fine up until the HTTPCaller that does the multipart/form-data upload.

 

 

Is there a way to fix this in the workflow or is it more likely to be a problem on the upload site?

 

 

 

Thanks!
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.

4 replies

jatoxa
Contributor
Forum|alt.badge.img+12
  • Author
  • Contributor
  • February 25, 2019

Is there no solution to this?

 

 

To put the problem simply how do I set the encoding in HTTP Caller when using multipart/form-data to upload a file?

 

 

 


Hello there,

I must chime in with the same bug:

German Umlauts read from a csv-file encoded in windows-1252 are replaced during upload as part of the multipart/form-data body. Each Umlaut (ä, ö, ü, ß) is substituted for an "ý".

Since the REST-endpoint accepts the same kind of data via SAS without issues and there is no error when using the service via the web frontend, I must assume that the http-caller does something buggy when reading the file for the multipart/form-data.

Is there a fix, a workaround or another kind of solution?

 

Cheers and best regards,

Matthias Daues

 


mirco
Contributor
Forum|alt.badge.img+1
  • Contributor
  • November 13, 2019

Whenever there are encoding problems maybe it's worth using the Pythoncaller.


_fabian_
Contributor
Forum|alt.badge.img+5
  • Contributor
  • May 11, 2021

I ended up with putting a TextEncoder Transformer in front of the HTTPCaller to URL-Encode the Attributes containing umlauts before passing them to the HTTPCaller, this works so far.

 

@matthiasdaues​  @jatoxa​  if this is still relevant for you