http-listener requires 'https' socket-binding, part 2 ----------------------------------------------------- Key: WFLY-5425 URL: https://issues.jboss.org/browse/WFLY-5425 Project: WildFly Issue Type: Bug Components: Web (Undertow) Affects Versions: 8.2.0.Final Reporter: Vsevolod Golovanov Assignee: Stuart Douglas Fix For: 9.0.0.Beta2 Continuing WFLY-2836. Is there a way to override {{http-listener}}'s {{redirect-socket}} attribute default value ("https") to be null? {quote}This is just default value, looking at the downside of not having default value for redirect-socket would be that people would not configure it, which would result in problems when having apps that require secure transport.{quote} Our app doesn't require secure transport. {code}redirect-socket=""{code} results in {noformat} Caused by: javax.xml.stream.XMLStreamException: ParseError at [row,col]:[956,166] Message: "JBAS014704: '' is an invalid value for parameter redirect-socket. Values must have a minimum length of 1 characters" {noformat} This: {code}redirect-socket="null"{code} treats it literally: {noformat} ]) - failure description: {"JBAS014771: Services with missing/unavailable dependencies" => ["jboss.undertow.listener.someapp-http-listener is missing [jboss.binding.null]"]} {noformat} So we're forced to have a https socket-binding. Which is not a "just define some binding" problem. It's a "negotiate with customers&sysadmins/document it/provide options to configure it" problem.