You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm not using the ControllerLinkBuilder because of the problems mentioned in that issue. But I can probably add code to Spring Data REST to also look for that header when setting a baseUri value (with the configuration value overriding even that).
It might also be nice to be able to plug in a component that would calculate a baseUri based on different criteria (a load-balancer, maybe?) instead of a static header value.
It would be the best solution to be able to provide your own strategy for this since using X-Forwarded-Host is not taking into account the protocol (it maybe https from the proxy, not http) and/or any additional path that proxy may have in-front of the URL...
Until this is implemented is there an easy way to provide this functionality? Can a new/custom/different bean be wired into this to do it?
The latest snapshots (and the M1 in the milestone repository) should deal with links differently since the self links are now rendered by the EntityLinks components and the baseUri is determined by the spring-hateoas machinery. Be interested to hear if that's the case.
This was recently added to spring-hateoas: spring-projects/spring-hateoas#33
Can this work for spring-data-rest as well?
Thanks.
The text was updated successfully, but these errors were encountered: