Forum Discussion

kkishore's avatar
kkishore
New Contributor III
4 years ago

Rest post zip file issue

Hi Team,

we are posting a zip file to the target location with restpost snap(invoking the webservice provided by target team), but below information is adding to the file and the zip file not able to open by the team.

Target team receiving the data like below adding extra content at header level:

-NpPpHQYDtTHWk9esbHreg29WnKx_bCYn
Content-Disposition: form-data; name=“file”; filename=“data.zip”
Content-Type: application/octet-stream; charset=UTF-8
Content-Transfer-Encoding: binary

actual data(zip format)

-NpPpHQYDtTHWk9esbHreg29WnKx_bCYn

how to avoid this extra content added to original zip file.

Please find the error here while target team trying to open the zip file stored in Blob field of Database.

5 Replies

  • mbowen's avatar
    mbowen
    Employee
    4 years ago

    Hi @kkishore

    I need to respond to another community post regarding REST POST behavior and will try to address your issue too. I know what you are referring to. Do you know the database the zip is being stored in?

  • kkishore's avatar
    kkishore
    New Contributor III
    4 years ago

    Hi @mbowen ,

    the data base is sql server. There is a table and storing the zip file in blob field

    • mbowen's avatar
      mbowen
      Employee
      4 years ago

      @kkishore
      Did you try changing the content type? I see that the content type is specified as application/octet-stream which is the default content type for the REST POST snap. Is this a single field upload? If so, try changing the content type to application/zip.

  • kkishore's avatar
    kkishore
    New Contributor III
    4 years ago

    Hi @mbowen ,

    Yes , it is single file upload, we had tried with content type as below options, but not working

    application/octet-stream
    multipart/x-zip
    application/zip
    application/zip-compressed
    application/x-zip-compressed

    • mbowen's avatar
      mbowen
      Employee
      4 years ago

      @kkishore

      Try this:

      The important points are that we’ve changed the Upload Body Type from Multipart form-data to Binary. That will prevent emitting the headers that you were seeing in the request body.

      However, that’s not enough, we also need to explicitly set the Content-Type via a HTTP header, otherwise, the content type will default to application/octet-stream. I think content type should be application/zip.

      Give this a shot and let me know.