Forum Discussion
Hi,
Sorry, I had thought from you're original post that it was your service under test that was setting that contentType, in which case adding the filename might be correct. Whereas it is infact SoapUI that is inserting the file name as part of the contentType property.
In the context of making a client call i.e. like SoapUI is doing in the Request TestStep, I must admit that I am not certain what purpose the filename would have when set as part of the contentType property, so could be a added unecessarily... I take it the actual PDF attachment is included as part of some kind of Base64 encoded multi-part message in the request?
Assuming the filename part of the contentType is a bug, does it cause your service an issue?
Thanks,
Rupert
Yes, it causes an issue (because there is a strict control on content type).
Regards,
Zouheir
Related Content
- 10 months agoKimdoengart
- 2 years agoTaz
Recent Discussions
- 17 hours agoGuhan-B
- 5 days agoruchisingh