<html><head><meta http-equiv="Content-Type" content="text/html charset=iso-8859-1"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;">Hi Nico<div><br></div><div>If you go to the admin settings of your IPT (<a href="http://localhost:8080/ipt-2.3-rc1/admin/config.do">http://localhost:8080/ipt-2.3-rc1/admin/config.do</a>) and set the base URL to <a href="http://10.209.1.58:8080/ipt-2.3-rc1">http://10.209.1.58:8080/ipt-2.3-rc1</a> does it work please?</div><div><br></div><div>Thanks,</div><div>Tim</div><div><br></div><div><br></div><div><br><div><div>On 04 Aug 2015, at 11:39, Nicolas Noé <<a href="mailto:n.noe@biodiversity.be">n.noe@biodiversity.be</a>> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite">
<meta http-equiv="content-type" content="text/html; charset=utf-8">
<div text="#000000" bgcolor="#FFFFFF">
<font size="-1"><font face="Verdana">Hi,<br>
<br>
I have just installed an instance of IPT 2.3RC on my Mac OS X
laptop using Tomcat 7 (manually installed).<br>
<br>
It's working perfectly fine as long as I access it on the local
machine, using localhost URLs. I'd like to make it accessible
from other hosts on the local network (to be used as a test
server during GB22 training events in Antananarivo).<br>
<br>
It seems the (generated) URLs for IPT static assets (CSS, JS,
...) always start with <a class="moz-txt-link-rfc2396E" href="http://localhost:8080/">"http://localhost:8080"</a>, even when the
page is requested from a different URL such as
<a class="moz-txt-link-freetext" href="http://10.209.1.58:8080/ipt-2.3-rc1">http://10.209.1.58:8080/ipt-2.3-rc1</a> . So from another machine, I
can get the basic page, but with 404 errors on all static files.<br>
<br>
I feel this is maybe related to
<a class="moz-txt-link-freetext" href="https://github.com/gbif/ipt/issues/817">https://github.com/gbif/ipt/issues/817</a>, and comes from the fact
that the IPT doesn't use the queried URL as a base for
generating other URLs. Is there an easy way for me to circumvent
this problem? Should I put a reverse proxy in front of Tomcat ?
Any sample, working configuration for that ?<br>
<br>
Thanks,<br>
<br>
Nicolas<br>
</font></font>
</div>
_______________________________________________<br>IPT mailing list<br><a href="mailto:IPT@lists.gbif.org">IPT@lists.gbif.org</a><br>http://lists.gbif.org/mailman/listinfo/ipt<br></blockquote></div><br></div></body></html>