Case-sensitive host-matching behaviour

[manugarg]

From [email protected] on September 16, 2013 13:06:54

What steps will reproduce the problem? Supplying a URL with different case formats, e.g., www.mydomain.com vs. WWW.mydomain.com, pacparser treats the two as different resources. What is the expected output? What do you see instead? The expected result of an evaluation like this should be identical in both cases, since hostnames are case-insensitive. However, I am getting two distinct results for what should be the same host. Explicitly converting strings to all lowercase causes both queries to return the identical, expected result. What version of the product are you using? On what operating system? 1.3.1 on OSX 10.8 Please provide any additional information below. According to the FAQ here: http://findproxyforurl.com/misconceptions/ "In order to perform host matching the host variable must be converted to lowercase. False. Implementing such code has been found unnecessary in all major browsers (Internet Explorer, Firefox, Chrome, and Safari). No browser has been found to require that the host be converted to lowercase in order to prevent case sensitive matching issues. Unlike URLs, hosts are case insensitive therefore any PAC rule mechanism should automatically assume case insensitivity when matching hosts."

cheers, Klaus

Original issue: http://code.google.com/p/pacparser/issues/detail?id=29