Mixing of query string and post body parameters

The specification defines in chapter 3.1:

> Data from the query string and the post body are aggregated into the request parameter set.

This may lead to following problems:

1\. The query string is usually used for non-hierarchical filtering of the addressed resources whereas the post body is used to send the data which should be stored or processed by the server. Both parameters at one time can be used by bulk operations like:

```
POST /articles?before=2014-01-01

archived=true
```

The only way to distinguish between both is manual parsing of getQueryString or the request body's input stream.

2\. The encoding of the post body can be changed by setCharacterEncoding(String enc) whereas the encoding of the query string is usually ISO-8859-1 and can't be changed. So the request parameter set may be populated with parameters encoded with different charsets.

Would it be possible to add at a method which helps to distinguish between both?