3 ms·

More likely that the developer didn't even think about it, I know I probably wouldn't.

• Filligree 9y ago
  You should! There are security implications galore, mostly due to the same-origin policy. Books can and have been written about web security; if you're writing webapps, you need to read one.
  • mattmanser 9y ago
    I'm not saying you shouldn't think about it, it's just a non-obvious vulnerability.
    • Filligree 9y ago
      Most of them are. Thus the book.
      • mattmanser 9y ago
        My feeling is that it's like computer security, you can bleat all you like about how the millions of developers have to magically know this stuff, or you can build it in by default. One method works, one doesn't. But keep on telling people to read a book, for all the good it will do.
        • Filligree 9y ago
          It's not like I'm in any position to do what you're suggesting. It's a bit late to revamp the entire web "security model" by this point.