network profile
| bio | website | |
|---|---|---|
| location | ||
| age | ||
| visits | member for | 1 year |
| seen | Jan 11 at 15:27 | |
| stats | profile views | 4 |
|
Apr 23 |
awarded | Popular Question |
|
Jan 11 |
comment |
Cookies + CSRF protection + AJAX Thank you for your response. I have accepted and upvoted your answer. Yes, I am referring to tokens; my question is not related to HTTP cookies at all. I am using one token per form and forcing HTTPS on the site, so it sounds like I should be okay. That said, if anyone knows of helpful resources that discuss use of one CSRF token per form (or session), I'd appreciate a link. |
|
Jan 11 |
accepted | Cookies + CSRF protection + AJAX |
|
Jan 11 |
asked | Cookies + CSRF protection + AJAX |
|
May 18 |
accepted | sanitizing likes/unlikes in application? |
|
May 18 |
comment |
sanitizing likes/unlikes in application? thank you for this answer. Accepted and upvoted. This is exactly what I was looking for. I hadn't heard about this clickjacking stuff, but will check it out, along with the CSRF cheat sheet (had it bookmarked). Codeigniter has built-in CSRF protection which I'm using, but I'm also reading about it and reviewing the code to learn as much as possible. Appreciate the rest of your advice also. |
|
May 18 |
comment |
sanitizing likes/unlikes in application? My question specifically says that I am using server-side validation! |
|
May 18 |
comment |
sanitizing likes/unlikes in application? I noticed your edit; appreciate it, but I don't need help with the JS function, it's already working. |
|
May 18 |
awarded | Commentator |
|
May 18 |
comment |
sanitizing likes/unlikes in application? Appreciate your response; my question is around sanitizing non-form inputs in a JS function--I'm not using PHP for this function, and have already sanitized inputs for those. |
|
May 18 |
revised |
sanitizing likes/unlikes in application? edited question |
|
May 18 |
asked | sanitizing likes/unlikes in application? |
|
May 14 |
comment |
header injection + codeigniter Now that I can upvote, I've upvoted this. |
|
May 14 |
comment |
header injection + codeigniter Now that I can upvote, it's upvoted! |
|
May 14 |
awarded | Supporter |
|
May 14 |
comment |
sanitizing input/output in php/codeigniter Thank you for this. I've upvoted your answer, as I already accepted D.W.'s. Much appreciated. |
|
May 14 |
accepted | sanitizing input/output in php/codeigniter |
|
May 14 |
comment |
sanitizing input/output in php/codeigniter Thanks, I didn't know that. Accepted and upvoted. And as a side note, I'm currently only doing server-side validation of data with Codeigniter's form validation. I may add client-side (jQuery/JS) at some point later. Security first! |
|
May 13 |
comment |
sanitizing input/output in php/codeigniter Appreciate your response. Actually I am reading through OWASP's paper on this topic--you recommended it--and I'm reading several other articles, too. Realizing that every input validation will need to be customized, and that most of my inputs fall into categories, I'm just trying to get a sense of whether there is something standard. As a front-end developer and designer, and only a few days into learning about application security, it makes it kind of tough to make final decisions based on reading without experience to rely on. |
|
May 12 |
awarded | Editor |
