(I remember the T5.1 patch wasn't pretty, by the way - the URL parser just threw a new RuntimeException so we decorated the service and had to parse the exception message looking for "the character 'X' at position X is not valid.") -- Steve ------------------------------- "If at first you don't succeed, so much for skydiving!"
On 23 February 2012 10:22, Steve Eynon <steve.ey...@alienfactory.co.uk> wrote: > Hiya, > > On these errors I usually patch T5 to return a 404 instead - that was > with some old T5.1 apps, I'm pretty sure we've done the same with T5.3 > but I'm not near the code at the moment... > > Steve > ------------------------------- > "If at first you don't succeed, > so much for skydiving!" > > > > > On 22 February 2012 05:27, trsvax <trs...@gmail.com> wrote: >> Thanks for the link. Something like that is pretty much what I want and I do >> run an Apache front end but I don't control that machine. Unfortunately I >> think my only real option is either a Tomcat filter or some Tapestry code. >> >> -- >> View this message in context: >> http://tapestry.1045711.n5.nabble.com/Vulnerability-Scanners-tp5503278p5503424.html >> Sent from the Tapestry - User mailing list archive at Nabble.com. >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org >> For additional commands, e-mail: users-h...@tapestry.apache.org >> --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
