How let ControllerLinkBuilder see original request URI?

[andrewtswu]

Hi,

Our tomcat server can only see internal URIs due to the way we setup our servers. If a client, for example, wants to get a list of events, the external URI is

http://api.mydomain.com/events

However, internally, tomcat sees

http://api.mydomain.com/servlet/events

which causes all self links to have similar pattern. For example

http://api.mydomain.com/servlet/events
http://api.mydomain.com/servlet/events/:id

Is there an easy way to customize ControllerLinkBuilder to re-write the URIs?

[collinpeters]

+1

[aleksz]

+1, but same goes to other link builders. In my scenario app is sitting behind the proxy. X-Forwarded-Host and X-Forwarded-Ssl do the trick, but I also need to change the path.

[dmartinpro]

As a workaround, you can rely on mod_substitute (
http://httpd.apache.org/docs/2.2/mod/mod_substitute.html).

On Mon, Apr 14, 2014 at 9:36 AM, Aleksandr Zhuikov <[email protected]

wrote:

+1, but same goes to other link builders. In my scenario app is sitting
behind the proxy. X-Forwarded-Host and X-Forwarded-Ssl do the trick, but I
also need to change the path.

Reply to this email directly or view it on GitHubhttps://github.com//issues/143#issuecomment-40339896
.

[aleksz]

Does it work for POST method returning status 201 and body? We are actually using it at the moment and it works for GET requests returning 200, but not for POST.

[nickgrealy]

Just wondering, would handling an X-Forwarded-Path header solve this issue? i.e.
nickgrealy@d069038

You could then automatically inject the headers as part of your application filters... e.g.
https://gist.github.com/nickgrealy/b4a582c8e1c411c5396d#file-application-java-L18-L24

I haven't committed to this project before, so let me know if I can go ahead and submit a pull request (do you want the HeaderOverrideFilter.java from the example included too?).

@aleksz - re: not working for POST - that sounds like a separate issue to this

[odrotbohm]

ControllerLinkBuilder already supports well-defined proxy server headers, so it's basically up to you making sure your proxy server sets those appropriately.

[otrosien]

Should be obsolete now. Current master is delegating this to UriComponentsBuilder, which is also base-path aware. (use X-Forwarded-Prefix header. see also https://jira.spring.io/browse/SPR-12500)

[gregturn]

Closed since we observe standard headers as well as support relative links as well.