On Thu, 22 Nov 2007 13:50:25 +0000, "Robert Synnott" rsynnott@gmail.com wrote:
but there may be a potential for breaking things; I don't think most clients will bother encoding semicolons, so things which previously worked might break. (Say, http://localhost/?phrase=this+is+a+test;+it+contains+a+semicolon )
Right, that's what I was fearing as well. If someone needs this desperately enough to send a patch, then it should be made configurable and the default should be that the semicolon as a separator is disabled.
Thanks, Edi.