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.
If I encode them (changing { to %7B and } to %7D), the request is
successful.
While I was not able to determine if that URL is valid (seems not
according to old RFC1738, but maybe yes, according to newer RFCs), I
have no control on that side.
All my users see is that this won't work with Squid, but will work without.
Was disallowing curly brackets a choice or is it a bug?
Perhaps there's some option to tweak?
bye & Thanks
av.
_______________________________________________
squid-users mailing list
squid-users@lists.squid-cache.org
http://lists.squid-cache.org/listinfo/squid-users
