Yes, you need to have the header `Access-Control-Allow-Origin: http://domain.com:3000` or `Access-Control-Allow-Origin: *` on both the OPTIONS response and the POST response. You should include the header `Access-Control-Allow-Credentials: true` on the POST response as well.

Your OPTIONS response should also include the header `Access-Control-Allow-Headers: origin, content-type, accept` to match the requested header.

I&#39;m trying to compile my program to a shared library that I can use from within Python code using ctypes.

The library compiles fine using this command:

    g++ -shared -Wl,-soname,mylib -O3 -o mylib.so -fPIC [files] `pkg-config --libs --cflags opencv`

However, when I try and import it using ctypes

    from ctypes import *
    mylib = CDLL(&quot;/path/to/mylib.so&quot;)
    print mylib.test() // Expected output: Hello World

I get the following error:

    libdc1394 error: Failed to initialize libdc1394

What&#39;s going on?



ctypes error: libdc1394 error: Failed to initialize libdc1394

I need to change out some buttons and text on a mobile website depending on whether the user is viewing it on an Android or iOS browser. Is there a reliable way to perform the check?

Detect if browser is running on an Android or iOS device

I&#39;m trying to make  CORS request POST from domain.com to a.domain.com. 

My javascript looks like this

    $(&#39;#fileupload&#39;).fileupload({
      xhrFields: {
        withCredentials: true
      },
      dataType: &#39;json&#39;,
      url: $(&#39;#fileupload&#39;).data(&#39;path&#39;),
      singleFileUploads: true,
      add: function(e, data){
        data.submit();
      }
    });

At first I see the OPTIONS route being called like so:

    Request URL: https://a.domain.com/some/route
    Request Method:OPTIONS
    Status Code:200 OK

**OPTIONS REQUEST:**    

    Access-Control-Request-Headers:origin, content-type, accept
    Access-Control-Request-Method:POST
    Host:a.domain.com
    Origin:http://domain.com:3000
    Referer:http://domain.com:3000/home

**OPTIONS RESPONSE**    

    Access-Control-Allow-Credentials:true
    Access-Control-Allow-Methods:POST
    Access-Control-Allow-Origin:http://domain.com:3000
    Connection:keep-alive
    Content-Length:0
    Content-Type:text/html;charset=utf-8

That request comes back with a 200 like stated. On my server, I have the same route with `POST` method and this is what I get in return after the `OPTIONS`

    Request URL:https://a.domain.com/some/route
**POST REQUEST**

    Content-Type:multipart/form-data; boundary=----WebKitFormBoundaryjwr5Pk7WBcfzMdbO
    Origin:http://domain.com:3000
    Referer:http://domain.com:3000/home

and the `POST` request gets canceled/fails. 

My question is, do I need to have the access-control-allow-origin on the POST controller as well? 

I have a cookie for authorization that has domain `.domain.com` that cookie got sent across once in a request and it&#39;s not being sent now. Any idea why that would happen? 




How do CORS and Access-Control-Allow-Headers work?

I'm trying to make CORS request POST from domain.com to a.domain.com.
My javascript looks like this
<pre><code class="hljs language-php">$('#fileupload').fileupload({
 xhrFields: {
 withCredentials: true
 },
 dataType: 'json',
 url: $('#fileupload').data('path'),
 singleFileUploads: true,
 add: function(e, data){
 data.submit();
 }
});
</code></pre>
At first I see the OPTIONS route being called like so:
<pre><code class="hljs language-less">Request URL: https://a.domain.com/some/route
Request Method:OPTIONS
Status Code:200 OK
</code></pre>
OPTIONS REQUEST:
<pre><code class="hljs language-less">Access-Control-Request-Headers:origin, content-type, accept
Access-Control-Request-Method:POST
Host:a.domain.com
Origin:http://domain.com:3000
Referer:http://domain.com:3000/home
</code></pre>
OPTIONS RESPONSE
<pre><code class="hljs language-makefile">Access-Control-Allow-Credentials:true
Access-Control-Allow-Methods:POST
Access-Control-Allow-Origin:http://domain.com:3000
Connection:keep-alive
Content-Length:0
Content-Type:text/html;charset=utf-8
</code></pre>
That request comes back with a 200 like stated. On my server, I have the same route with <code>POST</code> method and this is what I get in return after the <code>OPTIONS</code>
<pre><code class="hljs language-ruby">Request URL:https://a.domain.com/some/route
</code></pre>
POST REQUEST
<pre><code class="hljs language-bash">Content-Type:multipart/form-data; boundary=----WebKitFormBoundaryjwr5Pk7WBcfzMdbO
Origin:http://domain.com:3000
Referer:http://domain.com:3000/home
</code></pre>
and the <code>POST</code> request gets canceled/fails.
My question is, do I need to have the access-control-allow-origin on the POST controller as well?
I have a cookie for authorization that has domain <code>.domain.com</code> that cookie got sent across once in a request and it's not being sent now. Any idea why that would happen?

I have a situation where I&#39;m trying to use grunt to lint a codebase, excluding specific folders.

grunt uses minimatch (similar to bsdglob) under the hood to match files, but I can&#39;t seem to figure out how to do a .gitignore style exclude of a folder.

I&#39;d like to ingest this:

`ignoreme`

and match these:

    /folder/path/here/to/something/ok.js
    /another/folder/path.js
    /test.js

but not match these:

    /folder/ignoreme/something.js
    /folder/path/here/to/ignoreme/metoo/file.js

This will match everything, including ignoreme:

    /**/*.js

So I figured I could do something like:

    /**/!(ignoreme)/**/*.js

but that matches files in the ignoreme folder.

I&#39;m used to regexes, but can&#39;t seem to figure out how to repeat a pattern or something here - I also tried stuff like:

    /(!(ignoreme)|*)*/*.js

hoping the container would repeat, but that doesn&#39;t work, it just fails to match everything.

Any way to either pass a regex to grunt file paths, or make this work for me?

Update:
===

Here&#39;s how I&#39;m currently dealing with this issue:

    var pattern = /\/ignoreme\//
    var files = grunt.file.expandFiles(arrayOfFilesPassedToMinimatch).filter(function(f){
      return !pattern.test(f)
    })

I&#39;d still be interested if folder excludes are possible in minimatch.

grunt (minimatch/glob) folder exclusion

I recently asked [a question about LocalStorage][1]. Using `JSON.parse(localStorage.item)` and `JSON.parse(localStorage[&#39;item&#39;])` weren&#39;t working to return `NULL` when the item hadn&#39;t been set yet. 

However, `JSON.parse(localStorage.getItem(&#39;item&#39;)` did work. And it turns out, `JSON.parse(localStorage.testObject || null)` also works.

[One of the comments][2] basically said that `localStorage.getItem()` and `localStorage.setItem()` should always be preferred:

&gt; The getter and setter provide a consistent, standardised and
&gt; crossbrowser compatible way to work with the LS api and should always
&gt; be preferred over the other ways. -[Christoph][3]

I&#39;ve come to like using the shorthand dot and bracket notations for localStorage, but I&#39;m curious to know others&#39; take on this. **Is localStorage.getItem(&#39;item&#39;) better than localStorage.item or localStorage[&#39;item&#39;] OR as long as they work are the shorthand notations okay?**


  [1]: https://stackoverflow.com/questions/12623951/localstorage-get-item-with-dot-bracket-notation-not-working-with-json-parse
  [2]: https://stackoverflow.com/questions/12623951/localstorage-get-item-with-dot-bracket-notation-not-working-with-json-parse/12624333#comment17030808_12624333
  [3]: https://stackoverflow.com/users/1047823/christoph

Is localStorage.getItem(&#39;item&#39;) better than localStorage.item or localStorage[&#39;item&#39;]?

I have a simple delete button that will accept a string or number but won&#39;t accept an ng-model variable ( not sure if that&#39;s the correct terminology ).

    &lt;button class=&quot;btn btn-danger&quot; ng-click=&quot;delete(&#39;{{submission.id}}&#39;)&quot;&gt;delete&lt;/button&gt;

Which generates:

    &lt;button class=&quot;btn btn-danger&quot; ng-click=&quot;delete(&#39;503a9742d6df30dd77000001&#39;)&quot;&gt;delete&lt;/button&gt;

However, nothing happens when I click. If I hard code a variable then it works just fine. I assume I&#39;m just not doing things the &quot;Angular&quot; way, but I&#39;m not sure what that way is :)

Here&#39;s my controller code:

    $scope.delete = function ( id ) {
        alert( &#39;delete &#39; + id );
    }

How can you pass a bound variable to an ng-click function?

In chrome 22 &amp; safari 6.

Loading images from s3 for usage in a canvas (with extraction as a primary intent) using a CORS enabled S3 bucket, with the following code:

    &lt;!-- In the html --&gt;
    &lt;img src=&quot;http://s3....../bob.jpg&quot; /&gt; 

    // In the javascript, executed after the dom is rendered
    this.img = new Image();
    this.img.crossOrigin = &#39;anonymous&#39;;
    this.img.src = &quot;http://s3....../bob.jpg&quot;;

I have observed the following:

 1. Disable caches
 2. Everything works fine, both images load

Then trying it with caches enabled:

 1. Enable caches
 2. DOM image loads, canvas image creates a dom security exception
 
If I modify the javascript portion of the code to append a query string, like so:

    this.img = new Image();
    this.img.crossOrigin = &#39;anonymous&#39;;
    this.img.src = &quot;http://s3....../bob.jpg?_&quot;;

Everything works, even with caching enabled fully. I got on to the caching being a problem by using an http proxy and observing that in the failure case, the image isn&#39;t actually being requested from the server.

The conclusion I&#39;m forced to draw is that the image cache is saving the original request headers, which are then being used for the subsequent CORS enabled request - and the security exception is being generated due to violation of the same origin policy.

Is this intended behavior?

Edit: Works in firefox.

Edit2: Cors policy on s3 bucket

    &lt;?xml version=&quot;1.0&quot; encoding=&quot;UTF-8&quot;?&gt;
    &lt;CORSConfiguration xmlns=&quot;http://s3.amazonaws.com/doc/2006-03-01/&quot;&gt;
        &lt;CORSRule&gt;
            &lt;AllowedOrigin&gt;*&lt;/AllowedOrigin&gt;
            &lt;AllowedMethod&gt;GET&lt;/AllowedMethod&gt;
        &lt;/CORSRule&gt;
    &lt;/CORSConfiguration&gt;

I&#39;m using wide open because I&#39;m just testing from my local box right now. This isn&#39;t in production yet.

Edit3:  Updated cors policy to specify an origin

    &lt;?xml version=&quot;1.0&quot; encoding=&quot;UTF-8&quot;?&gt;
    &lt;CORSConfiguration xmlns=&quot;http://s3.amazonaws.com/doc/2006-03-01/&quot;&gt;
        &lt;CORSRule&gt;
            &lt;AllowedOrigin&gt;http://localhost:5000&lt;/AllowedOrigin&gt;
            &lt;AllowedMethod&gt;GET&lt;/AllowedMethod&gt;
        &lt;/CORSRule&gt;
    &lt;/CORSConfiguration&gt;

Verified outgoing headers:

    Origin	http://localhost:5000
    Accept	*/*
    Referer	http://localhost:5000/builder
    Accept-Encoding	gzip,deflate,sdch
    Accept-Language	en-US,en;q=0.8
    Accept-Charset	ISO-8859-1,utf-8;q=0.7,*;q=0.3

Incoming headers:

    Access-Control-Allow-Origin	http://localhost:5000
    Access-Control-Allow-Methods	GET
    Access-Control-Allow-Credentials	true

Still fails in chrome if I don&#39;t bust the cache when loading into the canvas.


Edit 4:

Just noticed this in the failure case.

Outgoing headers:

    GET /373c88b12c7ba7c513081c333d914e8cbd2cf318b713d5fb993ec1e7 HTTP/1.1
    Host	amir.s3.amazonaws.com
    User-Agent	Mozilla/5.0 (Macintosh; Intel Mac OS X 10_8_2) AppleWebKit/537.4 (KHTML, like Gecko) Chrome/22.0.1229.91 Safari/537.4
    Accept	*/*
    Referer	http://localhost:5000/builder
    Accept-Encoding	gzip,deflate,sdch
    Accept-Language	en-US,en;q=0.8
    Accept-Charset	ISO-8859-1,utf-8;q=0.7,*;q=0.3
    If-None-Match	&quot;99c958e2196c60aa8db385b4be562a92&quot;
    If-Modified-Since	Sat, 29 Sep 2012 13:53:34 GMT

Incoming headers:

    HTTP/1.1 304 Not Modified
    x-amz-id-2	3bzllzox/vZPGSn45Y21/vh1Gm/GiCEoIWdDxbhlfXAD7kWIhMKqiSEVG/Q5HqQi
    x-amz-request-id	48DBC4559B5B840D
    Date	Sat, 29 Sep 2012 13:55:21 GMT
    Last-Modified	Sat, 29 Sep 2012 13:53:34 GMT
    ETag	&quot;99c958e2196c60aa8db385b4be562a92&quot;
    Server	AmazonS3

I *think* this is the first request, triggered by the dom. I don&#39;t know that it isn&#39;t the javascript request though.

CORS policy on cached Image

I have several JS files so instead of copy and paste every one in the console window (Firefox and Chromium), I would want to call them from the shell if it is possible.

Every JS file has test functions that show if they are correct using console.log.

Is it possible to run JavaScript files from the command line?

I was browsing through the jQuery api and noticed that the [load method][1] is on the deprecated list.

&gt; Categories: Deprecated | Events &gt; Document Loading

I usually use this method to check if images are completly loaded. Why is it deprecated? And what am I supposed to be using instead?

  [1]: http://api.jquery.com/load-event/

load() method deprecated?

How can I trigger a function when I click anywhere on my page except on one div (`id=menu_content`) ?

jQuery click anywhere in the page except on 1 div

I recently upgraded my version of PHPStorm IDE and it now warns me about inefficient jQuery usage.

For example:

    var property_single_location = $(&quot;#property [data-role=&#39;content&#39;] .container&quot;);

Prompts this warning:

&gt; Checks that jQuery selectors are used in an efficient way. It suggests
&gt; to split descendant selectors which are prefaced with ID selector and
&gt; warns about duplicated selectors which could be cached.

So my question is:

&gt; Why is this inefficient and what is the efficient way to do the above selector?

I&#39;d guess at:

    var property_single_location = $(&quot;#property&quot;).find(&quot;[data-role=&#39;content&#39;]&quot;).find(&quot;.container&quot;);

Is this the right way?

Inefficient jQuery usage warnings in PHPStorm IDE

If I&#39;m working in a TypeScript .ts file, what can I do to get jQuery Intellisense/autocompletion when I type the $ character?

(I&#39;m working in an ASP.NET MVC 3 project in VS 2012.)

How do I get jQuery autocompletion in TypeScript?

I&#39;ve created a page with CSS. Now I must change from my editor to my browser and refresh the full page, just to have a look at every little change. But I don&#39;t want to refresh the page, because I have some animations.

So is there anything which I can use that my site updates automatically after a CSS update?  
Maybe with JavaScript, jQuery, Ajax or something?

Update the CSS of a Website without refreshing the Page

I&#39;m trying to set a header in my Go web server. I&#39;m using `gorilla/mux` and `net/http` packages.

I&#39;d like to set `Access-Control-Allow-Origin: *` to allow cross domain AJAX.

Here&#39;s my Go code:

    func saveHandler(w http.ResponseWriter, r *http.Request) {
    // do some stuff with the request data
    }

    func main() {
    	r := mux.NewRouter()
    	r.HandleFunc(&quot;/save&quot;, saveHandler)
    	http.Handle(&quot;/&quot;, r)
    	http.ListenAndServe(&quot;:&quot;+port, nil)
    }


The `net/http` package has documentation describing sending http request headers as if it were a client - I&#39;m not exactly sure how to set response headers?

Setting HTTP headers

I am having trouble getting a cross domain CORS request to work correctly using Chrome. 

Request Headers:

    Accept:*/*
    Accept-Charset:ISO-8859-1,utf-8;q=0.7,*;q=0.3
    Accept-Encoding:gzip,deflate,sdch
    Accept-Language:en-US,en;q=0.8
    Access-Control-Request-Headers:origin, content-type
    Access-Control-Request-Method:POST
    Connection:keep-alive
    User-Agent:Mozilla/5.0 (Macintosh; Intel Mac OS X 10_8_2) AppleWebKit/537.4 (KHTML, like Gecko) Chrome/22.0.1229.94 Safari/537.4

Response headers:

    Access-Control-Allow-Headers:*
    Access-Control-Allow-Origin:*
    Allow:GET, POST, OPTIONS
    Content-Length:0
    Date:Tue, 30 Oct 2012 20:04:28 GMT
    Server:BaseHTTP/0.3 Python/2.7.3

Error:

    XMLHttpRequest cannot load domain. Request header field Content-Type is not allowed by Access-Control-Allow-Headers.

And the python code serving the options request is:

    self.send_response(200)
    self.send_header(&#39;Allow&#39;, &#39;GET, POST, OPTIONS&#39;)
    self.send_header(&#39;Access-Control-Allow-Origin&#39;, &#39;*&#39;)
    self.send_header(&#39;Access-Control-Allow-Headers&#39;, &#39;*&#39;)
    self.send_header(&#39;Content-Length&#39;, &#39;0&#39;)
    self.end_headers()

It seems the `Access-Control-Allow-Origin` wildcard is being ignored?

CORS Access-Control-Allow-Headers wildcard being ignored?

I&#39;m creating a script that loads externally on other sites. It loads CSS and HTML and works fine on my own servers.

However, when I try it on another website it displays this awful error:

    Access-Control-Allow-Origin


Here you can see it loads perfectly: http://tzook.info/bot/

But on this other website it shows the error:
http://cantloseweight.co/robot/

I uploaded the loading script to jsfiddle:
http://jsfiddle.net/TL5LK/

I tried editing the htaccess  file like this:

    &lt;IfModule mod_headers.c&gt;    
        Header set Access-Control-Allow-Origin *
    &lt;/IfModule&gt;

Or like this:
  
    Header set Access-Control-Allow-Origin *


But it still doesn&#39;t work.



htaccess Access-Control-Allow-Origin

I&#39;m trying to perform a cross-domain POST request to an ASP.NET MVC controller action. This controller action accepts &amp; uses various parameters. The problem is that when the preflight request happens, the controller action actually attempts to execute &amp; because the OPTIONS request doesn&#39;t pass any data, the controller action throws out a 500 HTTP error. If I remove the code that uses the parameter, or the parameter itself, the entire request chain is completed successfully.

An example of how this is implemented:

**Controller Action**

    public ActionResult GetData(string data)
    {
    	return new JsonResult
    	{
    		Data = data.ToUpper(),
    		JsonRequestBehavior = JsonRequestBehavior.AllowGet
    	};
    }

**Client-side code**

    &lt;script type=&quot;text/javascript&quot;&gt;
            $(function () {
                $(&quot;#button-request&quot;).click(function () {
                    var ajaxConfig = {
                        dataType: &quot;json&quot;,
                        url: &quot;http://localhost:8100/host/getdata&quot;,
                        contentType: &#39;application/json&#39;,
                        data: JSON.stringify({ data: &quot;A string of data&quot; }),
                        type: &quot;POST&quot;,
                        success: function (result) {
                            alert(result);
                        },
                        error: function (jqXHR, textStatus, errorThrown) {
                            alert(&#39;Error: Status: &#39; + textStatus + &#39;, Message: &#39; + errorThrown);
                        }
                    };
    
                    $.ajax(ajaxConfig);
                });
            });
        &lt;/script&gt;

Now, whenever the preflight request happens, it returns a 500 HTTP code, because the &quot;data&quot;  parameter is null, seeing as the OPTIONS request doesn&#39;t pass any values.

The server application has been set up in my local IIS on port 8100 &amp; the page running the client-side code is set up on port 8200 to mimic the cross-domain calls.

I have also configured the host (on 8100) with the following headers:

    Access-Control-Allow-Headers: Content-Type
    Access-Control-Allow-Methods: POST, GET
    Access-Control-Allow-Origin: http://localhost:8200

One workaround I had found, was to check the HTTP method that executes the action &amp; if it&#39;s a OPTIONS request to just return blank content, otherwise execute the action code. Like so:

    public ActionResult GetData(string data)
    {
    	if (Request.HttpMethod == &quot;OPTIONS&quot;) {
    		return new ContentResult();
    	} else {
    		return new JsonResult
    		{
    			Data = data.ToUpper(),
    			JsonRequestBehavior = JsonRequestBehavior.AllowGet
    		};
    	}
    }

But this approach feels very clunky to me. I considered adding this sort of logic to an `Attribute`, but even this would mean decorating every action that will get called using CORS with it.

Is there a more elegant solution to getting this functionality to work?

Handling CORS Preflight requests to ASP.NET MVC actions

I&#39;m trying to enable CORS for all subdomains, ports and protocol.

For example, I want to be able to run an XHR request from http://sub.mywebsite.com:8080/ to https://www.mywebsite.com/*

Typically, I&#39;d like to enable request from origins matching (and limited to): 

`//*.mywebsite.com:*/*`

Content Type	Original Author	Original Content on Stackoverflow
Question	Leo Correa	View Question on Stackoverflow
Solution 1 - Javascript	monsur	View Answer on Stackoverflow

How do CORS and Access-Control-Allow-Headers work?

Javascript Problem Overview

Javascript Solutions

Solution 1 - Javascript

Detect if browser is running on an Android or iOS device

ctypes error: libdc1394 error: Failed to initialize libdc1394

Attributions