get

Currently to send a parameterized GET request to an API interface I am writing the following code: api/master/city/filter?cityid=1&citycode='ny' But I see that there is a limit on the URL length of 2,083 characters. To avoid this I would like to send the parameters in json format in the content body for a GET request. However, I see that none of the Get methods for the HttpClient allow for a content body to be sent. For the POST I could see there is a method within HttpClient named PostAsync that allows for a content body. Is there a way to send parameters for a GET request not in the URL in

I saw that we can write: <form method="link" action="foo.html" > <input type="submit" /> </form> To make a "link button". But I know we can write: <a href="foo.html" ><input type="button" /></a> Which will do the same. What's the difference? What's their browser compatibility? That page you link to is incorrect. There is no link value for the method attribute in HTML. This will cause the form to fall back to the default value for the method attribute, get , which is equivalent to an anchor element with a href attribute anyway, as both will result in a HTTP GET request. The only valid values of

As we all know, file uploading is most often accomplished using POST method. So, why can't the GET method be used for file uploads instead? Is there a specific prohibition against HTTP GET uploads? GET requests may contain an entity body RFC 2616 does not prevent an entity body as part of a GET request. This is often misunderstood because PHP muddies the waters with its poorly-named $_GET superglobal. $_GET technically has nothing to do with the HTTP GET request method -- it's nothing more than a key-value list of url-encoded parameters from the request URI query string. You can access the $