My application wants to distinguish GET parameters from POST parameters too, for the sake of generating a modified query string without submitted form data.
For instance, one page shows a master/detail database table. My table column headings link to e.g. "?sort=name&reverse=no" and will add or remove other attributes to show different slices of data. I want to preserve those accumulated query settings when the user submits a detail form at the bottom of the page.
This was easy enough for me to accomplish locally, using a custom filter.
I ''do not'' think this should necessarily become core CherryPy behavior, but it might not hurt to document the workaround somewhere.
BTW, there are of course other ways to skin this cat. I could have used sessions and cookies. But this is a pattern I've enjoyed in earlier PHP projects, and one that seems to work well for my users and their panoply of browsers.
Actually ''combining'' duplicate GET and POST parameters, I think, would only offer the worst of both worlds. Having POST take precedence makes more sense to me, and is best for my project, assuming it's documented to do that.