On 26/07/18 03:55, Andrea Venturoli wrote: > On 7/25/18 4:54 PM, Alex Rousskov wrote: >> On 07/25/2018 01:12 AM, Andrea Venturoli wrote: >>> On 7/22/18 3:29 PM, Andrea Venturoli wrote: >>> >>>>> http://xxxxxxxxxxx.xxxxxxxxxxx.xx/rest?method=navi_path.add&opera=I029&tipo=0&descr=XXXXXXXXX%20-%20Xxxxxxx%20xxxxxxxxxxx%20xxx%2030/12/2014%20-%20XXXX&xxxxx_xxxx=0¶ms={idDoc:%27C0002019%27,clasDoc:%27XXXXXX%27,nomeDoc:%27XXXXXXXXX%20-%20Xxxxxxx%20xxxxxxxxxxx%20xxx%2030/12/2014%20-%20XXXX%27,_X_TRACK_ID:%xxxxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx%27}&_ts=1532264445584&_dc=1532264445584 >>>>> >>> >>> >>> Upon furhter investigations, I see the problems are the curly braces. >> >>> Was disallowing curly brackets a choice or is it a bug? >> >> If your relaxed_header_parser is on, and Squid rejects URLs because they >> have curly braces in the path, then this is a Squid bug. >> >> N.B. relaxed_header_parser is on by default. > > I have no such option in my squid.conf, so it should be on. > I added it just to be sure the default wasn't off for some reason, but > it did not change. > > So, should I file a bug on https://bugs.squid-cache.org? > What is your "squid -v" output? If --disable-http-violations is used then relaxed parser will not include those "must never be transmitted in un-escaped form" (RFC 2396) characters. Amos _______________________________________________ squid-users mailing list squid-users@xxxxxxxxxxxxxxxxxxxxx http://lists.squid-cache.org/listinfo/squid-users
