Relative selfLinks + baseUrl

[kevinrenskers]

If my self link looks like this:

"self": {
    "link": "/conversations/1"
}, 

And I have the following configuration:

RestangularProvider.setBaseUrl('http://myapi.com/api');
RestangularProvider.setRestangularFields({selfLink: 'self.link'});

Then I would expect the element to have the link http://myapi.com/api/conversations/1. Sadly the url is instead http://localhost:8080/conversations/1 when running on localhost.

[mgonto]

You're right.

Marking this as bug.

Cheers

[kevinrenskers]

It would be great to have this fixed (and marked as a bug). When using a staging API and production API, we would really like to return relative self links, which currently doesn't work (and thus the API always needs to return full links).

[thegris]

First of all, self links are an awesome feature!

I'm running into this same issue. I am running locally with angular and REST endpoints being served from different ports. The relative href's are being interpreted as coming from the web URL, not the REST URL.

Thanks!

[Daanoz]

So, we just ran into this issue. Is there any update on this issue? We can work around it with a responseInterceptor but that's not really nice of course...

I see some open pull requests/comments, but not really a fix:

• Relative selfLinks + baseUrl #665 #682 (comment)
• Keep track of baseUrl root path and handle path-absolute resources. #851
• selfLink doesn't behave correctly with Cross-site baseurls #493

[yusufumac]

+1

[daviesgeek]

It looks like #851 was slated for release in 1.5.0. I reviewed the PR and hopefully we'll be able to get this merged in pretty soon