With bindAddress=0.0.0.0, codeserver uses hostname instead of IP-address

[dankurka]

Originally reported on Google Code with ID 8484

Found in GWT Release (e.g. 2.4.0, 2.5.1, trunk):
GWT 2.5.1


Encountered on OS / Browser (e.g. WinXP, IE9, FF10):
OSX 10.9, Chrome 31.0.1650.63 


Detailed description (please be as specific as possible):
It might be due to my own ignorance regarding the details
of GWT, but I experience the following inconvenience which
I suspect might be a bug:
When starting codeserver with bindAddress 0.0.0.0, it seems
to expect the GwtSourceMap.json to be located at 
   HOSTNAME:9876/sourcemaps/.../gwtSourceMap.json
rather than 
   IP-ADDRESS:9876/sourcemaps/.../gwtSourceMap.json
where HOSTNAME is the hostname of my local machine
and IP-ADDRESS is the address that is automatically allocated 
when I run my GWT web app with bindAddress 0.0.0.0.

This is apparent from the last line in the output when 
starting codeserver with bindAddress=0.0.0.0:
    [INFO] Next, visit: http://HOSTNAME:9876/
(actual hostname replaced by "HOSTNAME")

This results in two problems:
  1) The link specified in this last line will not work - the server is instead running
at IP-ADDRESS:9876. 
  2) Java sources are not available in the Chrome debugger due to a failed GET request
of the sourcemap file.


Workaround if you have one:
Explicitly specifying the correct bindAddress when starting the 
codeserver resolves the issue (but is suboptimal since this
address is dynamically allocated)

Reported by wouterboomsma on 2013-12-08 02:02:24

[dankurka]

@Brian I think I recently hit the same think on my macbook, is this how it is supposed
to work or could we improve this?

Reported by dankurka@google.com on 2013-12-16 05:59:43

• Status changed: NeedsInfo

[dsbecker]

https://gwt-review.googlesource.com/#/c/14300/

[dsbecker]

My code review for this fix needs a bump...

[tbroyer]

https://gwt-review.googlesource.com/14556