News for hackers. Stuff that matters.
Re:What is a Web Framework? by DasIch on Tuesday March 04, 2014 @03:13PM (#7342794)
You don't separate the headers from the body, producing a potential vulnerability for header injection or response splitting attacks. Both are severe security problems and both are easily avoided by using a web framework.

While it may not appear to be the case, developing secure web applications is rather complicated, that's why we have frameworks and that's why these frameworks can be somewhat complex. That doesn't make not using them the simpler solution.

Re:What is a Web Framework? by userbinator on Tuesday March 04, 2014 @10:00PM (#7344979)
> While it may not appear to be the case, developing secure web applications is rather complicated, that's why we have frameworks and that's why these frameworks can be somewhat complex. That doesn't make not using them the simpler solution.

I disagree. The more complexity you introduce, the more code is needed, the greater the chance of bugs, and the greater the chance of those bugs not being discovered sooner.

Re:What is a Web Framework? by js2 on Tuesday March 04, 2014 @08:51PM (#7344711)
You don't separate the headers from the body

Looks like it does to me. The content-type is printed with a \n and then Python implicitly adds a second newline. Or did you mean something else?

Re:What is a Web Framework? by DasIch on Tuesday March 04, 2014 @10:48PM (#7345153)
Hm, you're right. Response splitting and with that header injection should still be possible though, I think.

In any case having to manually make sure to print newlines in the right places and escape user input in headers correctly is insane.