Invalid URL characters via AJP

[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 assumption that 
the fronting service should be the line of defence?