Forum Discussion
POstman code
}
HTTP/1.1 503 Service Unavailable
Content-Type: application/json; charset=UTF-8
Date: Fri, 19 Jul 2019 14:24:52 GMT
Connection: close
Set-Cookie: visid_incap_2105598=ZJ31AESKTbPSMV0AAAAAQUIPAAAAAADhs9KF54LoNA+PTW1hdSoh; expires=Sat, 18 Jul 2020 08:05:12 GMT; path=/; Domain=.api.cl.cnb.com
Set-Cookie: incap_ses_1178_2105598=FrjFbh50lmNERlZELPSMV0AAAAAth/1g9xWAh0+Hs/BqO3Msg==; path=/; Domain=.api.com
Set-Cookie: ___utmcDzUZAFJWCu; path=/; Max-Age=900
Set-Cookie: ___utmYLZ=JrcDvHw; path=/; Max-Age=900
Set-Cookie: ___utmvbZ=tZz XIvOpalf: Wts; path=/; Max-Age=900
X-Iinfo: 11-4863546291402 97) q(0 0 1 -1) r(5 5) U6
X-CDN: Incapsula
Content-Encoding: gzip
Transfer-Encoding: chunked
{
"error_code": "11",
"error_message": "could not be sent"
}
I have put dummy urls and session ids etc above
Hi Soniawadhwa ,
It will be very helpfull if you paste any screenshot of both postman and soap ra request.
- richie5 years agoCommunity Hero
I asked for the RAW so I could see exactly what was published by both Postman and SoapUI and the responses for both. However - I'm not sure whether you did scrape the detail from the RAW - the reasons Im unsure is:
1. percent encoding of the '+' symbol in your URI - it looks like neither is encoding the plus - but I would've guessed Postman and ReadyAP! would encode the plus (there was a ReadyAPI! issue with plus symbols not being encoded - but this was a while ago and is fixed as far as I could tell).
2. On the postman request it appears that you have 2 Cache-Control headers on your Postman request - are you sure this is correct?
Ok - so - would it be possible to proxy your requests via fiddler so we can so exactly what is occurring (both requests and responses)? I thought we could get away with just checking the RAW - but fiddler is probably best.
Essentially we need to compare exaclty what is published - so this means payload and headers - both requests and responses - fiddler will give us the detail we need and at least we know there won't be a problem rendering the info wihtin Postman or SoapUI (which I've noticed can occur).
In regards to the Content-Type header on the SoapUI request - you appear to be setting it to application/json;charset=UTF-8 - but you don't include the charset reference in your Postman requests. Why are you specifying the additional charset parameter in the header? UTF-8 is the default charset for .json - so there's no point specifying it in the header
cheers,
rich
- Olga_T5 years agoSmartBear Alumni (Retired)
Thanks for your participation everyone!
Soniawadhwa, what stage are you on now? Could you please share your progress?
Thanks,
- Soniawadhwa5 years agoNew Contributor
I still haven't got it working. The endpoint in SOAPUI gives 503- Service unavailable with +1 ***-***-1234 in endpoint.
It is working in Postman. I even imported the postman collection in readyapi, but doesnt work
Related Content
Recent Discussions
- 4 days agominhng