Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    text
    copied!<p>I think the Flickr API returns the json as type 'text/plain' which then will be displayed as text. You might try 'text/json' as a halfway point. Being easily viewed might outweigh being correct in your case.</p> <p>Also consider that should any client require the content type to be 'application/json' and refuse to work with 'text/plain' that client should specifically request the type it wants without '<em>/</em>'. This then could be a case you look for when preparing the content type of your response, and you could document your service accordingly.</p> <p>See Request:</p> <pre><code>http://www.flickr.com/services/rest/?method=flickr.test.echo&amp;format=json&amp;api_key=cecc9218c59188ebc6150eff9cd908dc </code></pre> <p>Request Headers</p> <pre><code>Accept:application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5 Referer:http://www.flickr.com/services/api/response.json.html User-Agent:Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10_5_7; en-us) AppleWebKit/530.18 (KHTML, like Gecko) Version/4.0.1 Safari/530.18 </code></pre> <p>Response Headers</p> <pre><code>Connection:close Content-Encoding:gzip Content-Length:134 Content-Type:text/plain; charset=utf-8 Date:Thu, 02 Jul 2009 03:19:34 GMT P3p:policyref="http://p3p.yahoo.com/w3c/p3p.xml", CP="CAO DSP COR CUR ADM DEV TAI PSA PSD IVAi IVDi CONi TELo OTPi OUR DELi SAMi OTRi UNRi PUBi IND PHY ONL UNI PUR FIN COM NAV INT DEM CNT STA POL HEA PRE GOV" Vary:Accept-Encoding </code></pre> <p>Content</p> <pre><code>jsonFlickrApi({"method":{"_content":"flickr.test.echo"}, "format":{"_content":"json"}, "api_key":{"_content":"cecc9218c59188ebc6150eff9cd908dc"}, "stat":"ok"}) </code></pre>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload