Affects Version/s: 2.2.0, 2.3.0, 2.4.0
Fix Version/s: None
When wildcard binding for NameNode RPC is turned on (i.e. dfs.namenode.rpc-address=0.0.0.0:8020), HFTP download is failing.
Call to http://namenode:50070/data/.. returns the header Location with parameter nnaddr=0.0.0.0:8020, which is unlikely to ever succeed
The idea would be, if wildcard binding is enabled, to get read the IP address the request is actually connected to from the HttpServletRequest and return this one.
How to reproduce:
1. Turn on wildcard binding
2. Upload a file
3. Validate it's failing
4. Get more details via curl
We can clearly see the 0.0.0.0 returned as the NN ip.