GET/POST parameters question

hi

HTTP allows for parameters in the URL, and also you can submit parameters
in the body as well with mime types application/x-www-form-urlencoded or
multipart/form-data. Combining these in a single query has created
confusion in the FHIR community (a RESTful spec for healthcare). We're
being asking to say, in our specification, whether his is allowed,
required, or prohibited.

it seems to me that this is not something we should rule on in a derived
spec; either HTTP allows it for a good reason, and we should allow it, or
it's a bad idea and it shouldn't be allowed at the HTTP level. But we can't
find much good information about this on the web.

Has this been discussed? does this group have an opinion?

thanks
Grahame


-- 
-----
http://www.healthintersections.com.au / grahame@healthintersections.com.au
/ +61 411 867 065