Nexus 3.2 rejects requests when server name contains underscores

As the title says, when running Nexus on a server that contains an underscore in the hostname, Nexus rejects any requests and therefore doesn't work at all.

2017-09-22 12:22:22,393-0300 WARN [qtp245940153-65] *SYSTEM org.sonatype.nexus.internal.web.HeaderPatternFilter - rejecting request from xx.xxx.xxx.xx due to invalid header 'Host: myserver_name:8080'

I understand the desire to be compliant with RFC952 / RFC1123 which doesn't allow underscores in the hostname, but I believe some flexibility is needed here given that Windows and Active Directory happily allow hostnames with underscores and it's quite common to see server names with underscores in the enterprise.

In many scenarios, renaming a server is just not feasible, and creating an alternate DNS entry (without the underscore) causes confusion and is an unnecessary extra step that just makes it more difficult to adopt Nexus.