Contributions
Re: Problems in Ready API NG PRO with special charcaters like ÇÐÈÉÊËÌÍÎÏÑÒÓÔÖÕØÙÚÛÜÝÞß
Understood. I was thinking this might bea work-around to try, allowing users to stay onthe normal upgrade path. However, the maintenance build doesn't fix my problem - in SoapUI NG, the Raw view of the request showsM?ori ???? in a value, where in the Form view it hasMāori ĀĀāā (the header hasContent-Type: application/xml; charset=utf-8 ). the request fails server-side validation because of the '?' characters. This problem is resolved by adding-Dfile.encoding=UTF8 to the vmoptions file.9 years agoPlace ReadyAPI QuestionsReadyAPI Questions1.7KViews1like0CommentsRe: Problems in Ready API NG PRO with special charcaters like ÇÐÈÉÊËÌÍÎÏÑÒÓÔÖÕØÙÚÛÜÝÞß
While waiting for 1.5 to come out, here is something to try, which I found in aSmartBear Community post late last year, when I experienced a similar problem. Try adding-Dfile.encoding=UTF8 in the file ReadyAPI-1.4.0.vmoptions in the ReadyAPI bin directory under c:\Program Files\SmartBear - assuming UTF-8 is your choice ofencoding. I found I had to add this every time I upgraded since 1.3.0, for my tests to work. For the developer on this thread - if this is a valid work-around while waiting for 1.5 (hey, I'm trying to stay on topic:smileyhappy:) - in the forum I found both-Dfile.encoding=UTF8 (no hyphen) and-Dfile.encoding=UTF-8 (with the hyphen). Which is correct?9 years agoPlace ReadyAPI QuestionsReadyAPI Questions1.8KViews0likes2CommentsHow do I turn off requests going to Google Analytics and fast.wistia.com in SoapUI NG?
While trying to trouble-shoot requests from SoapUI NG, I fired up BurpSuite and set the proxy in Ready! API to localhost:8080. In addition tomy test's requests, the requests intercepted included ones to www.google-analytics.com and fast.wistia.com - every time I navigated around the SoapUI NG interface or ran a test. This raised a bunch of questions in my mind: Why are they there in the first place? Would this affect my SoapUI performance? Does this represent a potential privacy or security hole? Is my machine infected with something? While I can tell Burp Suite to ignore these, how can I turn them off? Thanks in advance for any help. Examples (note only Ready! API is set to use localhost:8080 proxy on this machine; I have closed the starter pages, only 1 test step open; fresh upgrade to version1.4.0): GET /embed/iframe_shim?domain=net HTTP/1.1 Accept-Language: en-us,en;q=0.5 Accept-Encoding: gzip Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7 Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8 Referer: http://smartbearsoftware.com/appindex/ready-starter-pages/pro/soapui-ng-starter-page.html User-Agent: Mozilla/5.0 (Windows NT 6.1; Win64; x64) AppleWebKit/537.44 (KHTML, like Gecko) JavaFX/8.0 Safari/537.44 Cache-Control: no-cache Pragma: no-cache Host: fast.wistia.com Proxy-Connection: keep-alive GET /Appindex/ready-starter-pages/pro/soapui-ng-starter-page.html HTTP/1.1 User-Agent: Java/1.8.0_45 Host: www.soapui.org Accept: text/html, image/gif, image/jpeg, *; q=.2, */*; q=.2 Proxy-Connection: keep-alive GET /collect?<whole bunch of parameters> Accept-Language: en-us,en;q=0.5 Accept-Encoding: gzip Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7 Referer: http://smartbearsoftware.com/appindex/ready-starter-pages/pro/soapui-ng-starter-page.html User-Agent: Mozilla/5.0 (Windows NT 6.1; Win64; x64) AppleWebKit/537.44 (KHTML, like Gecko) JavaFX/8.0 Safari/537.44 Cache-Control: no-cache Pragma: no-cache Host: www.google-analytics.com Accept: text/html, image/gif, image/jpeg, *; q=.2, */*; q=.2 Proxy-Connection: keep-aliveSolved4.1KViews0likes3Comments