Improve / better document case insensitive matching on routes / services


#1

Originally reported by & questioned on:

Currently the proxy respects case-sensitivity by default which is correct going by RFC 7230, however it is not very clear how to enable case-insensitivity for a route.

Currently, it is not documented as a functionality of the Regexes so you would have to deduce a pattern such as:

/(?i)terms

Would match:

/terms
/TerMs

Better documentation of this functionality would be very helpful to reduce tickets like above, or potentially create a boolean flag for insensitivity for ease-of-use and quality-of-life.