Re: Invalid URL characters via AJP

2019-02-06 Thread Mark Thomas
On 06/02/2019 14:05, George Stanchev wrote: > In light of recent changes around allowing and subsequent relaxation of the > invalid characters handling in TC, I just noticed that TC behind IIS (via JK > connector/AJP) happily accepts ";<> etc while the HTTP connector rejects > them. Is this how

Invalid URL characters via AJP

2019-02-06 Thread George Stanchev
In light of recent changes around allowing and subsequent relaxation of the invalid characters handling in TC, I just noticed that TC behind IIS (via JK connector/AJP) happily accepts ";<> etc while the HTTP connector rejects them. Is this how the AJP connector it is supposed to work? Is the ass