well, out of curiosity, what are the HTTP methods that accept parameters in the query string? they all? which HTTP methods in which the parameters have to be sent via cURL POSTFIELDS?
Share
Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
well, out of curiosity, what are the HTTP methods that accept parameters in the query string? they all? which HTTP methods in which the parameters have to be sent via cURL POSTFIELDS?
All request methods (
GET,HEAD,POST,OPTIONS,PUT,TRACE,DELETE,BREW) may have GET-style?x=yrequest parameters. It’s just very uncommon for some others (CONNECT).The reason is that HTTP deals with "resources", and it doesn’t actually care about URL parameters. Starting from the
/path delimiter it’s all just considered a resource name. Whether there are any?question marks in it, or the receiving webserver uses@in its place is irrelevant, because implementation-specific.HTTP clients obviously know about URL schemes and how to split them up, but it’s not a big concern for the protocol itself. I think the specification (RFC1616) makes little mention besides the URL scheme description. HTTPbis might be more elaborate.
If you have a POST-style request body with other methods actually depends less on the HTTP verb, but on the presence of a
Content-Type:andContent-Length:request header.