[jQuery] Re: parseerror on GET from window.location

2009-06-19 Thread James
That's a nice catch! On Jun 19, 12:10 am, Nick Fitzsimons wrote: > 2009/6/18 jacktanner : > > > > > > > I'm trying to do an AJAX GET. > > >            var q_url = window.location.toString(); > >            $.ajax({ > >                type: 'GET', > >                        url: q_url, > >      

[jQuery] Re: parseerror on GET from window.location

2009-06-19 Thread Nick Fitzsimons
2009/6/18 jacktanner : > > I'm trying to do an AJAX GET. > >            var q_url = window.location.toString(); >            $.ajax({ >                type: 'GET', >                        url: q_url, >                        cache: false, >                        dataType: 'json', >              

[jQuery] Re: parseerror on GET from window.location

2009-06-18 Thread pinku
hi, try to use escape function for your url. thanks prashant On Jun 18, 12:27 pm, jacktanner wrote: > When I hardcode q_url, I use a relative path. I tried > window.location.href (absolute path) and window.location.pathname > (relative path), and both of those give a parseerror. By the way, th

[jQuery] Re: parseerror on GET from window.location

2009-06-18 Thread jacktanner
When I hardcode q_url, I use a relative path. I tried window.location.href (absolute path) and window.location.pathname (relative path), and both of those give a parseerror. By the way, this is jquery 1.3.2. Thank you for explaning cache:false! On Jun 18, 2:04 pm, James wrote: > When you hardco

[jQuery] Re: parseerror on GET from window.location

2009-06-18 Thread James
When you hardcode q_url, do you also put in the absolute path? (e.g. http://www.balh.com/myscript.php) or only the relative path? (e.g. myscript.php) The _=1234567889 part is a result of using 'cache:false'. This gives the URL a unique value every time so that a server request is always done. On