Better use nxweb, this one isn't that secure: http://www.reddit.com/r/programming/comments/2bo44u/i_am_the...
Nope.c – A web framework with a tiny footprint
31–40 of 53 posts
Re: Nope.c – A web framework with a tiny footprint
#32Re: Nope.c – A web framework with a tiny footprint
#33Re: Nope.c – A web framework with a tiny footprint
#34Looking at the source code : https://github.com/riolet/nope.c/blob/c883b11df78bb8115d5e51... It tries to copy a buffer of 1024 byte (max) into a buffer of 512 bytes (by executing a request with an URL longer than 512 bytes). It also runs 15 children process and use blocking socket, meaning that it's easily "DoS'able". The overall code seems very "unsecure" and poorly designed.
Re: Nope.c – A web framework with a tiny footprint
#35Here's something that is probably safer and that actually scales: https://github.com/reginaldl/librinoo
Re: Nope.c – A web framework with a tiny footprint
#36https://github.com/datenwolf/litheweb
Lithweb is developed network API agnostic and requires no dynamic memory allocation (malloc/free). Its main target are microcontrollers and it has a memory footprint of as little as 0.5kiB. To make it work you'll have to provide an implementation of the ioops functions.
GET variable support has the scaffolding up, but URL parameter parsing not yet implemented.
However POST request support it fully implemented, including MIME Multipart reconstuction.
See the test/bsdsocket.c for an example on how to implement ioops and for a file upload example.
So far the repositry does not contain the tag nesting functions, but I have those, too.
Security issues? Probably some but so far not identified yet. However when I tried fuzzing it, the fuzzer got crashed by litheweb %) (litheweb was not impressed).
Re: Nope.c – A web framework with a tiny footprint
#37Re: Nope.c – A web framework with a tiny footprint
#38This site feels ridiculously fast. I've noticed that with other compiled frameworks too, e.g. CppCMS: http://cppcms.com/wikipp/en/page/main I wonder if it is just the lightweight HTML the websites use, or if there is really so much speed to gain from using a compiled language.
Commenters on this site had similar observations about D language's forum, which is written in D. http://forum.dlang.org/ Code: https://github.com/CyberShadow/DFeed If one insists on writing a webapp in a C/C++ like language, D might be the sane way to do it.
Re: Nope.c – A web framework with a tiny footprint
#39This site feels ridiculously fast. I've noticed that with other compiled frameworks too, e.g. CppCMS: http://cppcms.com/wikipp/en/page/main I wonder if it is just the lightweight HTML the websites use, or if there is really so much speed to gain from using a compiled language.
Commenters on this site had similar observations about D language's forum, which is written in D. http://forum.dlang.org/ Code: https://github.com/CyberShadow/DFeed If one insists on writing a webapp in a C/C++ like language, D might be the sane way to do it.
Re: Nope.c – A web framework with a tiny footprint
#40This site feels ridiculously fast. I've noticed that with other compiled frameworks too, e.g. CppCMS: http://cppcms.com/wikipp/en/page/main I wonder if it is just the lightweight HTML the websites use, or if there is really so much speed to gain from using a compiled language.
Yes, there are definitely huge speed gains possible and if you choose an implementation which is still interactive you get the benefits of both (I know one particular example in CL: teepeedee2, there are some blogs posts, e.g. http://john.freml.in/teepeedee2-c10k or so).