This site is the archived OWASP Foundation Wiki and is no longer accepting Account Requests.
To view the new OWASP Foundation website, please visit https://owasp.org
Difference between revisions of "Parameterized Command Interface"
From OWASP
(Reverting to last version not containing links to www.texteltdelrel.com) |
|||
| Line 1: | Line 1: | ||
{{Template:Stub}} | {{Template:Stub}} | ||
| − | + | {{taggedDocument | |
| + | | type=inactiveDraft | ||
| + | | lastRevision=2016-07-27 | ||
| + | | comment=Content is incomplete, poor content page | ||
| + | }} | ||
A parameterized command interface is used as an alternative to a string-based command interface. This type of interface prevents [[Injection]] attacks by keeping parameters separate from the command itself. | A parameterized command interface is used as an alternative to a string-based command interface. This type of interface prevents [[Injection]] attacks by keeping parameters separate from the command itself. | ||
Latest revision as of 02:10, 28 July 2016
This article is a stub. You can help OWASP by expanding it or discussing it on its Talk page.
This page contains draft content that has never been finished. Please help OWASP update this content! See FixME.
Last revision (yyyy-mm-dd): 2016-07-27
Comment: Content is incomplete, poor content page
Last revision (yyyy-mm-dd): 2016-07-27
Comment: Content is incomplete, poor content page
A parameterized command interface is used as an alternative to a string-based command interface. This type of interface prevents Injection attacks by keeping parameters separate from the command itself.
Examples of parameterized command interfaces include:
- PreparedStatement in Java
