json response is 'plain/text' type. Anyway to change type to 'application/json'?

Question

HeyA 3rd party's webservice response payload is a wellformed json fragment (wellformed json confirmed by doing a wellformed check in xmlspy),but the Content-Type header on response is 'plain/text' rather than 'application/json' meaning the payload in the response is represented as a single string of text in the response's Outline tab making creating assertions difficult.Before now when i wanted to change the type of the response (say from xml to json), i'd add an Accept header (value = application/json) to the request.However adding the Accept header to the request did NOT change the response's type from text to json.Would anyone have any ideas how i could get the response to be treated as json in ReadyAPI!s Outline tab?Could an event handler do this? i.e. not actually change the type of the response, but change how its represented in the Outline tab?Cheers!Rich

justinm89 · Answer

If you don't mind doing assertions through code, you could use JsonSlurper to take the response string and make it into an object like:
&nbsp;
import groovy.json.JsonSlurper

String responseStr = "" // wherever you get the response from
def response = new JsonSlurper().parseText(responseStr)// Perform assertions here (just making this stuff up)assert response.employees[0].id == 12345response.employees.each {   assert it.salary &gt; 0}
&nbsp;
Provided you're not trying to assert on some crazy complex stuff, this could work.&nbsp;

nmrao · Answer

Can't it possible to request the service provider to make it change?

richie · Answer

Hey Rao,Nah...it's an external 3rd party's webservice. :(Cheers,Rich

nmrao · Answer

3rd Party services? So what, if there is defect or issue arises, it must be addressed. Not sure what is obstructing not to make a request.

richie · Answer

JustinM89&nbsp; - cheers fella - I'll check this out
&nbsp;
nmrao&nbsp;- it's a defect from the perspective that the type specified doesn't reflect the payload content - but this doesn't change the payload content itself - so the API 'works successfully'. The requirements for this API only specifies the headers on the request - not the response.&nbsp; Furthermore - Its a well known 3rd party in use by lots of companies - the impact of changing the 'type' to what it should be won't make any difference to the API itself from a functional perspective - it will just make testing easier.
&nbsp;
Hence the reason there's no point raising it with the 3rd party.&nbsp; The API successfully responds with a .json fragment - its just hte Content-Type header that is 'incorrect'.&nbsp; Lots of other companies use this and haven't raised it as a ticket because excepting impacting performance sending as text/plain rather than application/json wont make any difference - or these other companies haven't noticed the issue - as I say - there's no functional impact - only a slight performance one.
&nbsp;
Cheers,
&nbsp;
rich
&nbsp;
&nbsp;
&nbsp;

Forum Discussion

json response is 'plain/text' type. Anyway to change type to 'application/json'?

Related Content

How to Validate Text/Plain response inside an xml

Does openapi 3 allow 200 response text/plain &&& 401 response application/json?

POSTING plain text via a property to a REST Service

Multiline string in readable format for mediatype application/json

Swashbuckle requests swagger.json as 'text/html' content type on server, not 'application/json'

Recent Discussions

Assert Step Not Executing All Assertions

Include external files (XML) for JDBC connection

Accessing database connection string from groovy test step

JDBC database connection pooling

JDBC "Some connection settings are not specified"