Weird JSON encoding using json_encode

Question

I'm using WordPress together with the JSON API Plugin (http://wordpress.org/extend/plugins/json-api/) to generate responses to our other site.

I've hit a really weird problem (we're using PHP 5.3.6), when I pass the following array http://pastebin.com/xdfYjrvK to json_encode() it gives me this (with json content-type): http://pastebin.com/T61XGPP5

So the crap in the beginning, in the above example it's 2609 and 0 in the end, it changes depending on the size of the response, more content -> higher hex number. It also appears only when the amount of response is "high enough", so it works on small responses.

First I thought it was the plugin, but it works locally (on two different machines Mac OS X) and we've updated all packages on the VPS (Debian, Apache, Nginx, PHP) to the latest versions.

It's only displayed when sending the content-type, not when outputting the $result with plain text instead of application/json:

$charset = get_option('blog_charset');
if (!headers_sent()) {
  header('HTTP/1.1 200 OK', true);
  header("Content-Type: application/json; charset=$charset", true);
}

echo $result;

$charset is set to utf-8.

The Google chrome console says: "Resource interpreted as Document but transferred with MIME type application/json."

So, does anyone have a clue whats happening here?

Yes, it comes from another function that takes care of the json_encoding with the built in. — Anders H
– Anders H, Commented Jun 28, 2011 at 14:09

frekw · Accepted Answer · 2011-06-29 06:40:43Z

4

This looks like chunked encoding (http://en.wikipedia.org/wiki/Chunked_transfer_encoding). Make sure to check that your headers are setting the Content-Length properly in the response to make sure you aren't forcing the web server to use CTE.

edited Jun 29, 2011 at 6:40

answered Jun 29, 2011 at 6:34

frekw

836 bronze badges

Sign up to request clarification or add additional context in comments.

2 Comments

Anders H Over a year ago

My headers were: HTTP/1.1 200 OK Server: nginx/0.6.32 Date: Wed, 29 Jun 2011 06:25:53 GMT Content-Type: application/json; charset=UTF-8 Transfer-Encoding: chunked Connection: keep-alive X-Powered-By: PHP/5.2.6-1+lenny10 Setting the content-length worked like a charm, thanks!

skiplecariboo Over a year ago

had the same problem, with nginx aswell.. thanks a lot this saved me a lot of trouble

Etu · Accepted Answer · 2011-06-28 13:32:57Z

0

One requirement json have is that all data you give to it must be UTF-8 encoded. json_encode() does not do this automaticly. So you can try to run this array_map("utf8_encode", $array); before you json_encode it.

Else... It looks weird, so Im just guessing...

answered Jun 28, 2011 at 13:32

Etu

413 bronze badges

Collectives™ on Stack Overflow

Weird JSON encoding using json_encode

2 Answers 2

2 Comments

Comments

Your Answer

Linked

Hot Network Questions

Collectives™ on Stack Overflow

2 Answers 2

2 Comments

Comments

Your Answer

Sign up or log in

Post as a guest

Linked

Related