On October 26, 2018 5:02:25 PM UTC, "M. Manna" <manme...@gmail.com> wrote: >Have you checked the connector config doc for relaxedPathChars and >relaxedQueryChars?
Those options have no impact on the parsing of the hist name. >On Fri, 26 Oct 2018 at 18:00, Amit Pande <amit.pa...@veritas.com> >wrote: > >> Hello all, >> >> Recent Tomcat versions (8.5.32 I think) has made a stricter >validation for >> hostnames with underscores in it. ( >> https://bz.apache.org/bugzilla/show_bug.cgi?id=62371) <snip/> >> The main issue for us now is that, since we ship Tomcat with our >product >> (IOW Tomcat runs in customer environments), this will break our >product >> functionality if customers have hostnames with underscore. Ideally, >they >> should correct the host names (to be RFC compliant) but customers >would be >> really averse to change hostname as it might a widespread change in >their >> environments. >> >> With Spring also, we ran into same issue but in later releases of >Spring >> this was fixed. I >> >> Would it be a good idea to make this strict check configurable so >that we >> can continue to cater to our customers without breaking the >functionality? The host names are invalid and should be fixed. Generally, Tomcat does not provide options to break spec compliance unless there is a compelling case to do so. I haven't seen such a case made for relaxing the host name parsing. >> Are there any other alternates to help solve this issue? Short of patching Tomcat yourself (not a course of action I recommend), no. Mark --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
