Forum Discussion

Burkhard's avatar
Burkhard
Occasional Contributor
6 years ago
Solved

REST Attachments: Not able to attach svg file in query

Hello all, I want to send a svg file in the Message body of a REST Put Request. I think that I set the correct content type "image/svg+xml" in the Attachments panel Nevertheless ReadyAPI send...
Burkhard's avatar
Burkhard
Occasional Contributor
6 years ago

Isn't this multi-form data?

 

richie's avatar
richie
Community Hero
6 years ago

Hi Burkhard 

 

Did you resolve your issue?   Apologies I've only just seen this post, but I had something similar maybe a year ago (I find the 'multipart/form-data' type/'Post QueryString' switch fiddly to use in ReadyAPI!).

 

I got it working eventually but with some help from the board- if you still haven't got it sorted I was going to trawl through the posts from a year ago - (but I'm a little reluctant to do this if you've fixed your issue!)

 

nice one,

 

rich

 

  • Burkhard's avatar
    Burkhard
    Occasional Contributor
    5 years ago

    Hi richie ,

    unfortunatley I'm still not able to solve that problem. I found a post here https://community.smartbear.com/t5/SoapUI-Pro/Update-Content-Type-in-Attachment-before-submission/m-p/41128 where the Content-Type in Attachment was changed before submission with help of event handler "RequestFilter.filterRequest" but I'm not able to get this handler working. So it would be really great if you could find some time to check your old posts how you fixed this problem.

    Best regards

    Burkhard

      • richie's avatar
        richie
        Community Hero
        5 years ago
        Hahaha! sonya_m you rock!

        That IS the post i was talking about....good spot!

        Burkhard. Ive been thinking more about your issue. Quick question. Are you sure your endpoint needs the REST query parms passed as content of the request payload? Switching the Post QueryString on sets the type to multiform type and i'm wondering if this is part of the problem. I know ive tested some endpoints that needed the query parms passed as part of the payload but ive also tested endpoints where i had the choice (so didnt!)

        If you set the type to the svg/xml and pass your query parms as part of the URI rather than payload this might help get around the issue without having to confuse things using multipart form type?

        If you need to use the multipart form type then i suggest reviewing the detail in the post that sonya_m found?

        Nice one

        Rich