How can a component get the host name (and protocol)?

Hello,

I need to build some absolute links (in the form "protocol://host/path") in a component, and these links should work both when the page is previewed in TeamSite and when it is published on the LiveSite runtime environment. My question is how can i determine at rendering time what the host name and the protocol (https for my teamsite server, but http for the runtime) are? I have tried various methods in the com.interwoven.livesite.runtime.RequestContext and in the HttpServletRequest, but all i get is variations on "localhost" (as the preview is behind a proxy?).

Is these an easy way to get this information?

Regs,
/t

Find more posts tagged with

Comments

AlexC

HttpServletRequest request = context.getRequest();
String url = request.getRequestURL();

This should give you a URL used for the request. See the javadoc for more info: http://java.sun.com/j2ee/sdk_1.3/techdocs/api/javax/servlet/http/HttpServletRequest.html

You may also get more info using the request.getHeader("referer") which is the URL that originated that click (yes the header name is misspelled, that is part of the RFC-2616, http://www.w3.org/Protocols/rfc2616/rfc2616-sec14.html#sec14.36).

tanguyr

AlexC,

Thanks for your reply.

HttpServletRequest request = context.getRequest();
String url = request.getRequestURL();

In TeamSite, this yields a url like:


http://localhost:38080/iw-preview/52616e646f6d49567396d247a467e23b335b46c7b7
aac337dcc78be0597b100642ea03a9c20006634dbe1a4abadd0c4bbf08fe5dcf230d6b/fy1krwi0.seed

request.getHeader("referer")

Again, in TeamSite this yields a url like:


https://wcms.dev.swift.com/iw-cc/command/iw.ccpro.list_directory?vpath
=//bewcmd01/default/main/www%5fswift%5fcom/WORKAREA/transport/sites/sdc/ordering/ordering%5fnews/rss%5ftest

Which looks great, except when i copy/paste the url into a new tab i get "null" for the referer. Since the component will be on a page which will be called directly (ie most visitors won't come from another page) i can't count on this being set.

Currently i've hacked together a ****-awful mess of code using java.net.InetAddress to get the machine name (luckily for me our machine names are strictly formatted and i can determine the environment by checking a single character in the name) and RequestContext.isRuntime(), but i'm still interested if anyone can point out a cleaner way to accomplish this.

Regs,
/t

AlexC

Can you post the HTTP header for any given request coming from the proxy, it may add a header part that includes the requested server.

tanguyr

Can you post the HTTP header for any given request coming from the proxy, it may add a header part that includes the requested server.

Thanks for the idea. I get the following headers:

On TeamSite:


host:localhost:38080
user-agent:Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.0.13) Gecko/2009073022 Firefox/3.0.13 (.NET CLR 3.5.30729)
accept:text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8
accept-language:en-us,en;q=0.5
accept-encoding:gzip,deflate
accept-charset:ISO-8859-1,utf-8;q=0.7,*;q=0.7
referer:https://wcms.dev.swift.com/iw-cc/command/iw.ccpro.list_nodes?vpath=//bewcmd01/default/main/www_swift_com/WORKAREA/transport/sites/sdc/ordering/ordering_news/rss_testcookie:iw_user=trademak; iw_which_ui=; iw_domain=; iwov_auth_bewcmd01=*052616e646f6d49567396d247a467e23b91c64a730b3a66fa5831ed00676c71ecf184a8f520061a805aab54cf54a7abe841decbbdff853292aa8030dae5eea52d2a462196e6d125fd; wprfl=default; CK_SDC_LANG=en; IWAUTH=52616e646f6d49567396d247a467e23b335b46c7b7aac337dcc78be0597b100642ea03a9c20006635948e3c1edbff459ac9dc71e1a71bd16; IWPROXY_PATHTRACK=/iw-mount/default/main/www_swift_com/WORKAREA/transport/favicon.ico
max-forwards:10
x-forwarded-for:172.24.106.149
x-forwarded-host:wcms.dev.swift.com
x-forwarded-server:bewcmd01-vip1.swift.com
x-forwarded-scheme:https

On the runtimes:


host:belsrd01:31776
user-agent:Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.0.13) Gecko/2009073022 Firefox/3.0.13 (.NET CLR 3.5.30729)
accept:text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8
accept-language:en-us,en;q=0.5
accept-encoding:gzip,deflate
accept-charset:ISO-8859-1,utf-8;q=0.7,*;q=0.7
keep-alive:300
connection:keep-alive
cookie:JSESSIONID=1D4ABF36C966D135DD9E547476BE110A
cache-control:max-age=0

I will investigate with the proxy admins if i can add x-forwarded-host and x-forwarded-scheme to the headers added by the proxy in front of the runtimes, that seems to be the shortest distance between where i am and a "clean" solution.

Thanks for your help with this.