[IPT] Static assets URLs

Tim Robertson trobertson at gbif.org
Tue Aug 4 11:46:38 CEST 2015


Hi Nico

If you go to the admin settings of your IPT (http://localhost:8080/ipt-2.3-rc1/admin/config.do) and set the base URL to http://10.209.1.58:8080/ipt-2.3-rc1 does it work please?

Thanks,
Tim



On 04 Aug 2015, at 11:39, Nicolas Noé <n.noe at biodiversity.be> wrote:

> Hi,
> 
> I have just installed an instance of IPT 2.3RC on my Mac OS X laptop using Tomcat 7 (manually installed).
> 
> 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).
> 
> It seems the (generated) URLs for IPT static assets (CSS, JS, ...) always start with "http://localhost:8080", even when the page is requested from a different URL such as http://10.209.1.58:8080/ipt-2.3-rc1 . So from another machine, I can get the basic page, but with 404 errors on all static files.
> 
> I feel this is maybe related to https://github.com/gbif/ipt/issues/817, 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 ?
> 
> Thanks,
> 
> Nicolas
> _______________________________________________
> IPT mailing list
> IPT at lists.gbif.org
> http://lists.gbif.org/mailman/listinfo/ipt

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.gbif.org/pipermail/ipt/attachments/20150804/465a55fd/attachment.html>


More information about the IPT mailing list