Contributions
Encoding of filename for MIME attachments
I'm using a REST service to upload files using MIME attachments. It should work withSwedish characters but the web service expects thefilename in the header to be encoded as utf-8 for non us-ascii characters to work. Inspected the request from both SoapUI and Postman using Fiddler and Postman correctly sets it utf-8 automatically. However, SoapUI does not and I can't figure out to set this. Tried changing the default file encoding in vmoptions, setting the ContentID according to RFC 2047 but without success. When using RFC 2047 encoding actually only "name" gets set but not filename. Any ideas?1.8KViews0likes3CommentsTwo-way SSL for REST
Hi, Tried unsuccessfully to gettwo-way SSL to work with the latest version of SoapUI (5.3.0). Followed this guide: http://geekswithblogs.net/gvdmaaden/archive/2011/02/24/how-to-configure-soapui-with-client-certificate-authentication.aspx I have aSSL key pair stored in a pfx with a password. The keystore is referred to in SoapUI settings and the password added there. "Requires client authentication" checkbox selected. I'm verifying using an openssl server that the client doesn't provide a certificate: 4294956672:error:140890C7:SSL routines:ssl3_get_client_certificate:peer did not return a certificate:s3_srvr.c:3296: SoapUI says "java.net.SocketException: Software caused connection abort: recv failed" Testing with a browser against the same serverprompts me to provide the certificate and the same pfx works in the browser. Am I missing something or is something broken in this version? I'm pretty sure I did exactly this in SoapUI a few years back.Solved9.7KViews0likes2CommentsRe: (Bug SoapUI 5.2.0) Very long endpoint names extend too far
Sorry about getting back to you late. I upgraded to 5.2.1 but the bug is still there. I've attached a SoapUI project where this issue can be observed. Open WeatherSoap TestSuite -> GetCityForecastByZIP TestCase -> GetCityForecastByZIP. The issue can be observed for the endpoint2.3KViews0likes2CommentsRe: (Bug SoapUI 5.2.0) Very long endpoint names extend too far
The endpoint URL is 310 characters andset on a SOAP Request (click edit current..). When adding a new endpoint with a shorter name the window still looks strangesince the long one still exists in the list of optional endpoints. I'm using the64-bit version on Windows 7.2.4KViews0likes4Comments(Bug SoapUI 5.2.0) Very long endpoint names extend too far
Hi, Found no other way to report it soadding it here. When endpoint names are very long the text field gets extended to the very far right of the window making it impossible to seethe buttons usually there. See attachment for example. Some visual truncation would be extremely useful. ThanksSolved2.4KViews0likes6Comments