-
Notifications
You must be signed in to change notification settings - Fork 840
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Relative selfLinks + baseUrl #665
Comments
You're right. Marking this as bug. Cheers |
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). |
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! |
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: |
+1 |
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 |
If my self link looks like this:
And I have the following configuration:
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.
The text was updated successfully, but these errors were encountered: