For JSON serialization, I'd assume it's because they're testing object serialization.
It's such a small, silly optimization. It doesn't bother me because it's not going to affect the overall results much, but I do feel it's against the spirit of the test. That kind of thing would be prevented if we made the test echo a request parameter, as was suggested elsewhere in the comments.
I'm not saying it's an especially useful benchmark, but it's intended to test something besides raw response speed.
> I'm not saying it's an especially useful benchmark, but it's intended to test something besides raw response speed.