Ajax api call with relative url about boomerang

[bluesmoon]

Shouldn't r_url be set to /json/my.json to make it an absolute path? Without that it would be relative to the current page.

[nicjansma]

@cyang05 I couldn't get your test case to work (without Boomerang):

Try this: http://dev.nicj.net/auto-xhr/

The page has your code, as above. The URL it's passing to $.ajax() is auto-xhr/test.json, which you're saying should go to http://dev.nicj.net/auto-xhr/test.json.

I agree with Philip, that a relative URL without a leading slash such as auto-xhr/test.json would be relative to the current path http://dev.nicj.net/auto-xhr, and thus should be http://dev.nicj.net/auto-xhr/auto-xhr/test.json.

Is this only in a specific browser you're seeing this behavior?

What if you switch to a leading /?

[nicjansma]

@cyang05 Are you by chance using an Angular app or something that uses history pushState? I may see an issue, where the "relative url" for an angular app is / while the method we use to cleanup the URL in plugins/auto_xhr.js might consider the history state URL (/some/page)

[cyang05]

We have a base tag inside our head element:
""
I think all relative url should be relative to host root.

[cyang05]

And I think JQuery takes the base tag into consideration. I just tested your code with base tag, it worked.

And yes, we are using angular framework.

[nicjansma]

@cyang05 I updated the repro at http://dev.nicj.net/auto-xhr, but I still can't seem to reproduce the problem.

I also tried on a site that has Angular with a base href set, but couldn't reproduce there either.

Can you share the URL you're seeing the issue on?

Also, can you let me know what browser + OS you've found this on?

[cyang05]

Someone loads this js file in our repo:
https://c.go-mpulse.net/boomerang/QB2NF-KYJFR-YPPM5-YJF6X-LAMRA
After comment it out, our website goes back to normal. The code was never in production. We found the problem on our local testing server.
Since boomerang is in that js file, we speculate it's caused by boomerang and apparently it's not.

Thanks for your time, I really appreciate it.

[bluesmoon]

It looks like you're using mPulse, which is the commercial service that uses boomerang. The mPulse team is already in communication with your developers regarding this issue.

[nicjansma]

FYI, we have resolved this issue in mPulse and will be back-porting this to boomerang.js