Note that there are some explanatory texts on larger screens.

plurals
  1. POWhat is the correct way to make web form input safe for a variety of contexts?
    primarykey
    data
    text
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. COI'm specifically interested in making data safe for use within the application after it has already passed through a simple validation layer that checks the general format of the response but doesn't look for say, SQL injection or other threats. Basically ways to handle the data that will not result in significantly destructive behavior by the program.
      singulars
    2. COI had in mind something along the lines of: User input might get wrapped in a sort of wrapper that prevents code from using it in unsafe ways. That input might then need to be unwrapped in a particular way that makes it difficult for someone to UNKNOWINGLY do something unsafe with it. The code using it would need to ensure it was made safe for use in the context of that code before using it. Is there something like this that has been established?
      singulars
    3. COYou mention at one point that you want something broad and flexible and at another point that you were imagining a framework of sorts. So you don't want a simple solution in the sense of "doing this one thing will scrub the input" so much as "doing this one thing will trigger 10 other things automatically that will scrub input", is that right? I'm not trying to be cheeky, I'm just unsure if you are looking for a method or a tool. More to come...
      singulars
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload