TJ, thanks for you indepth reply and the link to the Wiki post. Point
well taken from both you and Walter. One thing I will definitely do
before anything else is redirect tonerize.com to www.tonerize.com, so
that I can alleviate any of these issues before I make all of the
calls relative!
Thanks
Wow you were right that was exactly the issue. I know you can't use
Ajax cross-domain but I had no idea that putting in the full URL would
cause problems. It was also very strange because it only happened on
certain computers / browsers.
Regardless, thanks so much for your help!
On Apr 7, 1:27 p
Hi,
Sorry, sent too soon. When I said "aren't the same thing," I mean in
terms of the Same Origin Policy[1].
[1] http://en.wikipedia.org/wiki/Same_origin_policy
HTH,
-- T.J.
On Apr 7, 7:00 pm, "T.J. Crowder" wrote:
> Hi,
>
> > However on some computers the request is never even sent, and we
Hi,
> However on some computers the request is never even sent, and we can't
> figure out why.
Have you eliminated things like what brand of browser they're using,
etc.?
Walter's point about the URL well-taken, and I see that you've already
fixed it for the bit he mentioned. That's a good idea
Is there a reason why you are using complete URLs in your call?
var categoriesInitUrl = 'http://www.tonerize.com/catalog/picker/categories/'
;
You might get better mileage by making these relative URLs.
var categoriesInitUrl = '/catalog/picker/categories/';
Walter
On Apr 7, 2009, at 10:52 AM
