title: HTML5 Canvas, the operation is insecure, but it's my own image
body: <p>I have an image stored in a different directory than my javascript, like so:   "../part1/part2/part3/image.png"</p>
  
  <p>If I try to render it to a canvas, then call getImageData on it, I get "The Operation is Insecure". </p>
  
  <p>A cursory google search shows that this often happens for cross origin images. Which is all well and good, but it's my image, on my own server.  </p>
  
  <p><strong>Is having a ".." in the path really enough to set the Cross Origin flag, or should I look for alternate causes for the message?</strong></p>
  
  <p>My objective is to have images stored in a parent directory that any of several different subdirectories (with their own html and javascript) can access. Is this a bad practice, and if so, are there alternatives? </p>
  
  <p>Edit: Slightly more digging shows that local files are considered cross origin by default, which is indeed how I am testing.  It's all well and good if this will work in production, but I want to test BEFORE putting it on my server. Any tips?</p>
  
  <p>Edit: Yeah, I wasn't running a server. Guess there really isn't a better way then, huh?</p>