A simple HTTP(S) based file upload service written in C

https://github.com/sora-chan/wakaba

You're not going to be able to make anything near nginx's level of quality and stability in C in a sane amount of time.

Maybe if you're a mental midget. I write perfect, correct, optimal C the first time I write it and I'm done in a matter of days. And it's not because I'm good at programming but because C is the just the right level of abstraction to obtain these results the first time around. So you're using a buffer? Check the buffer length. Ok, it's good. It's as easy as that. The problems happen when people code without thinking about what they write.

But if it uses openssl it's fucked.

>>6

The problems happen when people code

Well, of course. Nobody should code, they should program instead. Do you code, >>6-kun?

sora-chan here.
https://wakaba.dhcp.io for more info.

>>8
i think what you made is cool, well done

>>8
This is nice. Will it stay up? I might use it for small file sharing if that's okay with you.

>>10
It will stay up for as long as i can keep it up, however i don't have very much bandwidth, so I don't know how long that will be.
But if one person is using it, I'll keep it up, I didn't spend time working on it for nothing.

Although it might be a bit unstable for the next few days (not really sure) because there is a bug in openssl's SSL_accept that randomly causes a segfault, i think it's got something to do with my multithreaded code, but it might take a while to fix.
The server's already crashed once in the small amount of time it's been up.

>>6
This, you need to be in the right kind of mindset when programming C.
I find that being home helps the most, code produced in public usually turns out to be shit and just gets reverted and rewritten when i get back home anyway

openssl was created by the JEWS to subvert the goyim!

>>11
Don't blame openssl for something that is very likely to be YOUR fault:
http://linux.die.net/man/3/crypto_lock

>>14
So, is this similar to mutex's or something?
I just lock and unlock at every SSL_accept call?
This doesn't seem like a very friendly interface, how the fuck are these used?

>>15
No, OpenSSL does the locking/unlocking. You tell it what functions to use to do that.

unlock my anus

>>16
Hi there!

You seem to have made a bit of a mistake in your post. Luckily, the users of /prog/ are always willing to help you clear this problem right up! You appear to have used a tripcode when posting, but your identity has nothing at all to do with the conversation! Whoops! You should always remember to stop using your tripcode when the thread it was used for is gone, unless another one is started! Posting with a tripcode when it isn't necessary is poor form. You should always try to post anonymously, unless your identity is absolutely vital to the post that you're making!

Now, there's no need to thank me - I'm just doing my bait to help you get used to the anonymous text-board culture!

>>18
Fuck off with your /g/ meme bullshit.

>>19
sage is not a downvote gro

>>20
>>19 wasn't downvoting, ey was telling you to fuck off while not bumping the thread.

>>22
You seem to have gotten dubs with your post. Luckily, the users of /prog/ are always willing to check your dubs right up! You appear to have gotten a post number ending in repeating digits when posting! Great! We will always remember to check your dubs when the board you are posting in is a textboard! Posting with a dubs when it is always necessary is great form. We will always try to check your dubs following the culture of the site, since your dubs are absolutely vital to the post that you're making!

Now, there's no need to thank us - we're just doing our best to help your GET in the text-board cultu

>>22
how did you predict dubs?

>>23
The post above mine was 21, so I knew mine would be 22 (unless somebody was luckier and got it before me).
In the end, it's all gambling!