ansaurus

Question

Why does jQuery.get('/home/user/0/0a.html') fail when using file: rather than http:?

Answer 1

A:

I'd start by closing your  tags, and seeing how it works then.

Also, you really should be binding events with $().bind('click', function(){}) or $().click(function(){}) rather than onclick.

Are you using Firebug, or looking at the error console?

I get a mismatched tag. Expected: . error after clicking the first one. However, they all work for me.

Make sure that the files exist and the path is correct.

Here is a version with more jQuery like binding:

<html>
  <head>
    <script type="text/javascript" src="file:////var/duck/js/jquery-1.4.2.js"></script>

    <script>
      $(document).ready(function(){
        $('#p_1').click(function(){
          $.get('/home/user/whatever.html','',function(a{alert(a);});
        });
      });
    </script>
  </head>
    <body>
      <p id='p_1'>
        Get /home/user/0/1/2/3/4/4a.html
      </p>
      <p id='p_2'>
        Get /home/user/0/1/2/3/4/resources/4ra.html
      </p>
      <p id='p_3'>
        Get /home/user/0/0a.html
      </p>
      <p id='p_4'>
        Get /home/user/0/1/2/3/resources/3ra.html
      </p>
    </body>
  </html>

Fill in the binds for each . There are tons of ways you could link the elements to the preferred files, actually - delegation, arrays, indexes, etc.

Alex JL 2010-07-05 20:15:50

Closing tags produced no change.

C.W.Holeman II 2010-07-05 20:18:26

You know that not closing them is making each section part of the previous elements, right? Or it would, but Firefox is fixing your HTML for you. You must close your tags. This HTML is invalid. It would probably blow up worse in IE.

Alex JL 2010-07-05 20:26:12

Weird, I closed them and now get `mismatched tag. Expected: </BODY>.`. Oh.. apparently FF is being case sensitive on the tags.

Alex JL 2010-07-05 20:30:02

Produces the same results as the code in the question.

C.W.Holeman II 2010-07-05 21:13:20

Regardless, I'd suggest working with binding events in jQuery in this style rather than onclick, which is kind of archaic. Be sure to include the `$(document).ready()`. It worked for me, so I'm thinking it just can't locate the file you're requesting.

Alex JL 2010-07-05 21:31:10

Answer 2

+2 A:

I may be wrong, but I have a feeling it's failing because $.get() follows the Same origin policy when processing a request and since /home/user/whatever is not a valid link and instead a filepath, it fails there.

I recommend taking the 2 minutes it takes to run a quick test server and try it with real URL's within your local domain.

If you have Python installed it's as simple as typing this in a terminal:

python -m SimpleHTTPServer

Bartek 2010-07-05 20:16:27

I thought of same-domain restrictions too, and I've heard of people having problems with Ajax and file:/// vs. using an actual webserver. He does say that the first two work, though.

Alex JL 2010-07-05 20:18:32

file:///home/user/0/0a.html produces the same result.

C.W.Holeman II 2010-07-05 20:23:36

That's not what I told you to do?

Bartek 2010-07-05 20:33:36

The two that work are at the same level or lower in the file tree while the failures require access higher than the starting directory.

C.W.Holeman II 2010-07-05 20:36:11

I too strongly suggest installing (or using, one might already be installed on Ubuntu) a webserver, perhaps Apache. Developing on a webserver is a much better plan than files.

Alex JL 2010-07-05 20:38:21

Answer 3

A:

security.fileuri.strict_origin_policy is preventing access. To correct enter about:config in the address bar, then change the value from true to false for security.fileuri.strict_origin_policy which will grant access to all of the files using scheme file: in addition to http:.

In long, starting point for this info came from Bartek's use of the the term Same origin policy and the Wikipedia link in his answer.

From Browser Security Handbook, part 2 - project hosting on Google Code:

Firefox 3 is currently the only browser that uses a directory-based scoping scheme for same-origin access within file://. This bears some risk of breaking quirky local applications, and may not offer protection for shared download directories, but is a sensible approach otherwise.

From Mozilla Developer Center Same-origin policy for file: URIs:

Starting in Gecko 1.9, files are allowed to read only certain other files. Specifically, a file can read another file only if the parent directory of the originating file is an ancestor directory of the target file.

but,

The new security.fileuri.strict_origin_policy preference, which defaults to true, can be set to false if the user doesn't want to strictly enforce the same origin policy on file: URIs.

So, the second two files bumped into this restriction which can be addressed by changing the security.fileuri.strict_origin_policy.

Note that enabling access in other parts of the hierarchy does not grant any more access than is allowed by the file system directly.

C.W.Holeman II 2010-07-06 17:34:36

ansaurus

tags:

views:

answers:

Why does jQuery.get('/home/user/0/0a.html') fail when using file: rather than http:?

related questions