in reply to Crash-Test Dummies: A Few Thoughts on Website Testing
It appears my post here is related; disregard if not.
Years ago, I wrote an accounting application for an ISP. It used CGI::Application. I forced the system to use only one entry point and to error out on any URL passed in that wasn't from this entry point.
I then implemented CGI::Application::Plugin::LinkIntegrity to protect against rogue URL input, after entry has been gained.
Although specific to CGI::Application, it wouldn't be hard to drum up something similar for any other module or even custom code. This, along with -T and other routine validation should make things a bit more resistant to tampering.
|
|---|
| Replies are listed 'Best First'. | |
|---|---|
|
Re^2: Crash-Test Dummies: A Few Thoughts on Website Testing
by Your Mother (Archbishop) on Oct 12, 2015 at 21:56 UTC | |
by Anonymous Monk on Oct 12, 2015 at 23:53 UTC |