i&#39;m trying using cURL for a GET request like this:


    function connect($id_user){
        $ch = curl_init();
        $headers = array(
        &#39;Accept: application/json&#39;,
        &#39;Content-Type: application/json&#39;,
    
    	);
        curl_setopt($ch, CURLOPT_URL, $this-&gt;service_url.&#39;user/&#39;.$id_user);
     	curl_setopt($ch, CURLOPT_HTTPHEADER, $headers);
        curl_setopt($ch, CURLOPT_HEADER, 0);
        $body = &#39;{}&#39;;
    
        curl_setopt($ch, CURLOPT_CUSTOMREQUEST, &quot;GET&quot;); 
        curl_setopt($ch, CURLOPT_POSTFIELDS,$body);
        curl_setopt($ch, CURLOPT_RETURNTRANSFER, true);
     
        // Timeout in seconds
        curl_setopt($ch, CURLOPT_TIMEOUT, 30);
     
        $authToken = curl_exec($ch);
     
        return $authToken;
    }

As you an see i want to pass $body as the request&#39;s body , but i don&#39;t know if its correct or not and i can&#39;t debug this actually, do you know if is the right to use  `curl_setopt($ch, CURLOPT_POSTFIELDS,$body);` with a GET request?

Cause this enteire code works perfect with POST, now i&#39;m trying change this to GET as you can see

PHP cURL GET request and request&#39;s body

    &lt;script src=&quot;http://ajax.googleapis.com/ajax/libs/jquery/1.3.2/jquery.js&quot; type=&quot;text/javascript&quot;&gt;&lt;/script&gt;
    &lt;script&gt;
    $.get(&quot;http://example.com/&quot;, function(data) {
         alert(data);
    });
    &lt;/script&gt;

it does an OPTIONS request to that URL, and then the callback is never called with anything. 

When it isn&#39;t cross domain, it works fine.

Shouldn&#39;t jQuery just make the call with a `&lt;script&gt;` node and then do the callback when its loaded? I understand that I won&#39;t be able to get the result (since it is cross domain), but that&#39;s OK; I just want the call to go through. Is this a bug, or am I doing something wrong?

Why am I getting an OPTIONS request instead of a GET request?

I just wondered if there is a very easy way (best: a simple `$this-&gt;container-&gt;isGet()` I can call) to determine whether the request is a `$_POST` or a `$_GET` request.

According to the docs,

&gt; A Request object holds information about the client request. This
&gt; information can be accessed via several public properties:
&gt; 
&gt; - `request`: equivalent of `$_POST`;
&gt; - `query`: equivalent of `$_GET` (`$request-&gt;query-&gt;get(&#39;name&#39;)`);

But I won&#39;t be able to use `if($request-&gt;request)` or `if($request-&gt;query)` to check, because both are existing attributes in the Request class.

So I was wondering of Symfony offers something like the

    $this-&gt;container-&gt;isGet();
    // or isQuery() or isPost() or isRequest();

mentioned above?

How can I check if request was a POST or GET request in Symfony2 or Symfony3

I am using the latest okhttp version: **okhttp-2.3.0.jar**

How to add query parameters to GET request in okhttp in java ?

I found a [related question][1] about android, but no answer here!


  [1]: https://stackoverflow.com/questions/29875325/add-query-params-to-a-get-request-in-okhttp-in-android

How to add query parameters to a HTTP GET request by OkHttp?

Consider this form:
```html
&lt;form action=&quot;http://www.blabla.com?a=1&amp;b=2&quot; method=&quot;GET&quot;&gt;
    &lt;input type=&quot;hidden&quot; name=&quot;c&quot; value=&quot;3&quot; /&gt; 
&lt;/form&gt;
```
When submitting this `GET` form, the parameters `a` and `b` are disappearing.  
Is there a reason for that?  
Is there a way of avoiding this behaviour?


When submitting a GET form, the query string is removed from the action URL

I need to do an [HTTP GET][1] request in JavaScript. What&#39;s the best way to do that?

I need to do this in a Mac OS X dashcode widget.

  [1]: http://en.wikipedia.org/wiki/Hypertext_Transfer_Protocol#Request_methods


HTTP GET request in JavaScript?

I want to be able to create a custom AngularJS service that makes an HTTP &#39;Get&#39; request when its data object is empty and populates the data object on success.

The next time a call is made to this service, I would like to bypass the overhead of making the HTTP request again and instead return the cached data object.

Is this possible?

Cache an HTTP &#39;Get&#39; service response in AngularJS?

Is there a limit to the length of a GET request?

I&#39;m developing a new RESTful webservice for our application.

When doing a GET on certain entities, clients can request the contents of the entity.
If they want to add some parameters (for example sorting a list) they can add these parameters in the query string.

Alternatively I want people to be able to specify these parameters in the request body. 
[HTTP/1.1][1] does not seem to explicitly forbid this. This will allow them to specify more information, might make it easier to specify complex XML requests.

My questions:

  * Is this a good idea altogether?
  * Will HTTP clients have issues with using request bodies within a GET request?

https://www.rfc-editor.org/rfc/rfc2616


  [1]: https://www.rfc-editor.org/rfc/rfc2616

HTTP GET with request body

When you GET

   https://encrypted.google.com/search?q=%s

Is the `%s` query encrypted? Or just the response?
If it is not, why should Google serve its public content also with encryption?


Is GET data also encrypted in HTTPS?

How can I do an HTTP GET from a Un*x shell script on a stock OS X system? (installing third-party software is not an option, for this has to run on a lot of different systems which I don&#39;t have control on).

For example if I start the Mercurial server locally doing a *hg serve*:

    ... $ hg serve 

And then, from a Linux that has the *wget* command I do a wget:


    ... $  wget http://127.0.0.1:8000
    --2010-12-31 22:18:25--  http://127.0.0.1:8000/
    Connecting to 127.0.0.1:8000... connected.
    HTTP request sent, awaiting response... 200 Script output follows
    Length: unspecified [text/html]
    Saving to: `index.html

And on the terminal in which I launched the *&quot;hg serve&quot;* command, I can indeed see that an HTTP GET made its way:

    127.0.0.1 - - [30/Dec/2010 22:18:17] &quot;GET / HTTP/1.0&quot; 200 -

So on Linux one way to do an HTTP GET from a shell script is to use *wget* (if that command is installed of course).

What other ways are there to do the equivalent of a *wget*?  I&#39;m looking, in particular, for something that would work on stock OS X installs.



OS X: equivalent of Linux&#39;s wget

I&#39;ve been getting the same old error every time I test a new `URL` from my browser&#39;s address bar when I&#39;m `returning Json` (using the built-in `MVC JsonResult helper`):

&gt; This request has been blocked because sensitive information could be disclosed to third party web sites when this is used in a `GET request`. To allow `GET requests`, set `JsonRequestBehavior` to `AllowGet`.

Rather than grunt in acknowledgement and fire up Fiddler to do a post request, this time, I&#39;m wondering exactly what it is that a `GET` request exposes that a `POST` request doesn&#39;t?

What &#39;sensitive information&#39; could be disclosed when setting JsonRequestBehavior to AllowGet

I have a HTTP GET request that I am attempting to send. I tried adding the parameters to this request by first creating a `BasicHttpParams` object and adding the parameters to that object, then calling `setParams( basicHttpParms )` on my `HttpGet` object. This method fails. But if I manually add my parameters to my URL (i.e. append `?param1=value1&amp;param2=value2`) it succeeds.

I know I&#39;m missing something here and any help would be greatly appreciated.

How to add parameters to a HTTP GET request in Android?

I have a set of resources whose representations are lazily created. The computation to construct these representations can take anywhere from a few milliseconds to a few hours, depending on server load, the specific resource, and the phase of the moon.

The first GET request received for the resource starts the computation on the server. If the computation completes within a few seconds, the computed representation is returned. Otherwise, a 202 &quot;Accepted&quot; status code is returned, and the client must poll the resource until the final representation is available.

The reason for this behavior is the following: If a result is available within a few seconds, it needs to be retrieved as soon as possible; otherwise, when it becomes available is not important.

Due to limited memory and the sheer volume of requests, neither NIO nor long polling is an option (*i.e.* I can&#39;t keep nearly enough connections open, nor even can I even fit all of the requests in memory; once &quot;a few seconds&quot; have passed, I persist the excess requests). Likewise, client limitations are such that they cannot handle a completion callback, instead. Finally, note I&#39;m not interested in creating a &quot;factory&quot; resource that one POSTs to, as the extra roundtrips mean we fail the piecewise realtime constraint more than is desired (moreover, it&#39;s extra complexity; also, this is a resource that would benefit from caching).

I imagine there is some controversy over returning a 202 &quot;Accepted&quot; status code in response to a GET request, seeing as I&#39;ve never seen it in practice, and its most intuitive use is in response to unsafe methods, but I&#39;ve never found anything specifically discouraging it. Moreover, am I not preserving both safety and idempotency?

So, what do folks think about this approach?

__EDIT__: I should mention this is for a so-called business web API--not for browsers.

Is it wrong to return 202 &quot;Accepted&quot; in response to HTTP GET?

Do querystring parameters get encrypted in HTTPS when sent with a request?

Are querystring parameters secure in HTTPS (HTTP + SSL)? 

I can decorate an action either with the [AcceptVerbs(HttpVerbs.Post)]/[AcceptVerbs(HttpVerbs.Get)] 

    [AcceptVerbs(HttpVerbs.Post)]
    public ActionResult Create(string title)
    {
        // Do Something...
    }

or with the [HttpPost]/[HttpGet] attributes

    [HttpPost]
    public ActionResult Create(string title)
    {
        // Do Something...
    }

Are they different?



What is the difference between [AcceptVerbs(HttpVerbs.Post)] and [HttpPost]?

How to add indexes to array in query string?

I tried send data like this:

    axios.get(&#39;/myController/myAction&#39;, { params: { storeIds: [1,2,3] })

And I got this url:

    http://localhost/api/myController/myAction?storeIds[]=1&amp;storeIds[]=2&amp;storeIds[]=3

So, I should to get this url:

    http://localhost/api/myController/myAction?storeIds[0]=1&amp;storeIds[1]=2&amp;storeIds[2]=3

What I should add in my params options to get this url?

How to correctly use axios params with arrays

From what I can gather, there are three categories:

1. Never use `GET` and use `POST`
2. Never use `POST` and use `GET`
3. It doesn&#39;t matter which one you use.

Am I correct in assuming those three cases? If so, what are some examples from each case?

When do you use POST and when do you use GET?

I&#39;m trying to build a restful `API` and I&#39;m struggling on how to serialize `JSON` data to a `HTTP query string`. 

There are a number of mandatory and optional arguments that need to be passed in the request, e.g (represented as a JSON object below): 

    {
       &quot;-columns&quot; : [
          &quot;name&quot;,
          &quot;column&quot;
       ],
       &quot;-where&quot; : {
          &quot;-or&quot; : {
             &quot;customer_id&quot; : 1,
             &quot;services&quot; : &quot;schedule&quot;
          }
       },
       &quot;-limit&quot; : 5,
       &quot;return&quot; : &quot;table&quot;
    }

I need to support a various number of different clients so I&#39;m looking for a standardized way to convert this json object to a query string. Is there one, and how does it look?

Another alternative is to allow users to just pass along the json object in a message body, but I read that I should avoid it (https://stackoverflow.com/questions/978061/http-get-with-request-body/978173).

Any thoughts?

**Edit for clarification:**

Listing how some different languages encodes the given json object above:

 - `jQuery` using `$.param`: -columns[]=name&amp;-columns[]=column&amp;-where[-or][customer_id]=1&amp;-where[-or][services]=schedule&amp;-limit=5&amp;return=column
 - `PHP` using `http_build_query`: -columns[0]=name&amp;-columns[1]=column&amp;-where[-or][customer_id]=1&amp;-where[-or][services]=schedule&amp;-limit=5&amp;return=column
 - `Perl` using `URI::query_form`: -columns=name&amp;-columns=column&amp;-where=HASH(0x59d6eb8)&amp;-limit=5&amp;return=column
 - `Perl` using `complex_to_query`: -columns:0=name&amp;-columns:1=column&amp;-limit=5&amp;-where.-or.customer_id=1&amp;-where.-or.services=schedule&amp;return=column

jQuery and PHP is very similar. Perl using complex_to_query is also pretty similar to them. But none look exactly the same.

Standardized way to serialize JSON to query string?

**Update**

The accepted answer was good for last year but today I would use the package everyone else uses:
https://github.com/mikeal/request

---

**Original**

I&#39;m trying to grab google&#39;s logo and save it to my server with node.js.

This is what I have right now and doesn&#39;t work:

			var options = {
				host: &#39;google.com&#39;,
				port: 80,
				path: &#39;/images/logos/ps_logo2.png&#39;
			};
			
			var request = http.get(options);
			
			request.on(&#39;response&#39;, function (res) {
				res.on(&#39;data&#39;, function (chunk) {
					fs.writeFile(dir+&#39;image.png&#39;, chunk, function (err) {
						if (err) throw err;
						console.log(&#39;It\&#39;s saved!&#39;);
					});
				});
			});

How can I get this working?

All Http Get Solutions on Gang of Coders

Total of 20 Http Get Solutions

PHP cURL GET request and request's body