tracker issue : CF-4203405

select a category, or use search below
(searches all categories and all time range)
Title:

ColdFusion connector will throw a 400.0 error with FQDN with an underscore in them

| View in Tracker

Status/Resolution/Reason: Closed/Fixed/Fixed

Reporter/Name(from Bugbase): Michael Little / ()

Created: 10/24/2018

Components: Installation/Config, Connector

Versions: 2016,11.0,2018

Failure Type: Non Functioning

Found In Build/Fixed In Build: 2016.0.07.311392 / CF2016U12,CF2018U5

Priority/Frequency: Normal / All users will encounter

Locale/System: ALL / Win 2012 Server x64

Vote Count: 0

Problem Description: ColdFusion 2016 connectors will generate a 400.0 error when handling a web site where the hostname has an underscore in it. 

Steps to Reproduce: Windows 2012 Server, IIS 7.5, ColdFusion 2016 with Update 7. Create a web site with two bindings, one with test_test.adobe.com and testtest.adobe.com. The first site will throw an error and the second will not. Admittedly, underscores are generally frowned upon in hostnames, but we noticed this with a couple of legacy web sites. Update 6 and before had no issue with it.       

Actual Result: 400.0 IIS Error

Expected Result: Web page is displayed

Any Workarounds: DNS edits

Attachments:

Comments:

I've encountered a couple entries in my log files where we use a wildcard domain using IIS. Apparently both browsers and IIS support sub-domains with underscores and dashes, but Tomcat doesn't and throws an error. The result is a "400 Bad Request" error and lots of info in the coldfusion-error.log file. org.apache.coyote.AbstractProcessor parseHost INFO: The host [_dmarc.website.com] is not valid Note: further occurrences of request parsing errors will be logged at DEBUG level. java.lang.IllegalArgumentException org.apache.coyote.AbstractProcessor parseHost INFO: The host [www-.website.com] is not valid Note: further occurrences of request parsing errors will be logged at DEBUG level. java.lang.IllegalArgumentException: The character [.] is not valid after a hypen in a domain name.
Comment by James M.
31079 | July 30, 2019 03:42:40 PM GMT