Pabe1975
Occasional Contributor
Joined 6 years ago
User Profile
User Widgets
Contributions
Re: Replacing + character with %2B when sending
Hi nmrao; It is a soap request I am sending. Yes it is a POST (see snippet). In the RAW the + is still visible however when processing it in a HTTP JMS Gateway the + is translated to a space character. A snippet of the post: POST http://localhost:XXXX?q=XXX.XXXXXX.XXXX.Aanvraag.1.XX.Queue&token=XXXXXX HTTP/1.1 Accept-Encoding: gzip,deflate Content-Type: application/soap+xml;charset=UTF-8;action="XXXXXXXX" Content-Length: 10458 Host: localhost:20511 Connection: Keep-Alive User-Agent: Apache-HttpClient/4.5.2 (Java/1.8.0_181) . . . . <Naam>Dhr. R. Pleaseman</Naam> <Emailadres>regressiezakelijk1@lip.woesap.com</Emailadres> <TelefoonnummerMobiel>00+31 (0)6-29 60 01 163</TelefoonnummerMobiel> <NotificatieVoorkeur>GEEN</NotificatieVoorkeur> <ContactKenmerk>Contactpersoon Uitvoering</ContactKenmerk>2.2KViews0likes3CommentsReplacing + character with %2B when sending
When sending a http request with a + in the a field (in this case a field that contains an international phone number with + XX XXXX) the + is replaced with a space. However in the receiving endpoint needs the +, is there a way to replace the + with %2B so a + character is sent to the receiver ? We don't want the %2B in the field as it confuses people so we want to handle this issue 'behind the screens'.Solved2.4KViews0likes5CommentsRe: Response message automatically encoded to base64
This is the correct solution: Add the RequestFilter.afterRequest event handler with this string to decode the response - def encodedResp = context.httpResponse.responseContent def decodedResp = encodedResp.decodeBase64() String toText = new String (decodedResp) context.httpResponse.responseContent = toText The script will be executed on receiving each response, and you will see the decoded response content in the XML, Outline and Overview tabs. In this article, you will find more details about handling events - https://support.smartbear.com/readyapi/docs/testing/handling-events.html4.2KViews1like2CommentsRe: Response message automatically encoded to base64
Hi Richie; Unfortunately the -1 value did not resolve my problem. Channeling through fiddler is something I still need to set up. The weird thing is that is the first service of which the response is auto-encoded to base64. It does not seem to have any relation to the size of the response returned as far as I can see. Will let everyone know when I found the solution via Fiddler as it might help others with similar problems. The reason I mentioned the CDATA because it is referred to in deh Smartbear documentation.4KViews0likes0CommentsResponse message automatically encoded to base64
Hi All; I wonder if someone came across this issue and has a way to solve it. I am getting an valid SOAP response from the service and that does not have a CDATA section in it. When receiving it in ReadyApi (2.60) the response is automatically encoded to base64. This does not happen for other services I am using and when debugging the message in NJams I get a normal response from the service. Of course I have looked into the base64 encoding option that is in the settings of ReadyApi and the compression limit setting is empty. I have tried putting in a large value so the message falls within the limit set in the option (so it is not encoded). Hopefully someone can give me a hand. Thanks in advance ! PaulSolved4.6KViews0likes9Comments