]
Xavier Coulon commented on JBIDE-20107:
---------------------------------------
Will be fixed for 4.3.0.Beta2.
The current workaround for desktop browsers is to use the LiveReload extension instead. It
will work even if the application connects on port 8080.
Browser connects on port 8080 instead of livereload custom port
---------------------------------------------------------------
Key: JBIDE-20107
URL:
https://issues.jboss.org/browse/JBIDE-20107
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: livereload
Affects Versions: 4.3.0.Alpha2
Reporter: Xavier Coulon
Assignee: Xavier Coulon
Priority: Critical
Fix For: 4.3.0.Beta2
When selecting a module and calling {{Show In>Web browser via LiveReload}}, the
browser connects on the default HTTP port of the app server instead of connecting on the
LiveReload custom port (something like {{54321}}.
Digging with curl, it seems that the URL used to connect does not contain a trailing
'/' and in return, WildFly responds with a {{302}} response and a new location
which passes through the 8080 port:
{code}
curl -v
http://192.168.0.10:55201/conferenceschedule
* Hostname was NOT found in DNS cache
* Trying 192.168.0.10...
* Connected to 192.168.0.10 (192.168.0.10) port 55201 (#0)
> GET /conferenceschedule HTTP/1.1
> User-Agent: curl/7.37.1
> Host: 192.168.0.10:55201
> Accept: */*
>
< HTTP/1.1 302 Found
< Date: Wed, 17 Jun 2015 14:55:33 GMT
< X-Powered-By: Undertow/1
* Server WildFly/8 is not blacklisted
< Server: WildFly/8
< Location:
http://192.168.59.103:8080/conferenceschedule/
< Date: Wed, 17 Jun 2015 14:55:33 GMT
< Content-Length: 0
<
* Connection #0 to host 192.168.0.10 left intact
{code}