Got linked to this article today, NoSQL Data Modelling Techniques. I don’t think I’m going to have the time to read it, but I skimmed it, and maybe someone else will be interested. It talks about various data modelling strategies and their implications.
I was configuring MediaWiki to allow uploads and was getting an error in the browser about the POST data being too large (“does not allow request data with POST requests, or the amount of data provided in the request exceeds the capacity limit.”). I had a look in the Apache error log and found:
[Thu Feb 23 16:12:45 2012] [error] [client 60.240.67.126] request body exceeds m aximum size (131072) for SSL buffer, referer: https://www.jj5.net/morpheus/Speci al:Upload [Thu Feb 23 16:12:45 2012] [error] [client 60.240.67.126] could not buffer messa ge body to allow SSL renegotiation to proceed, referer: https://www.jj5.net/morp heus/Special:Upload
So I did some research. I found this document, File upload size which suggested editing /etc/php5/apache2/php.ini which I did:
upload_max_filesize = 20M post_max_size = 80M
That didn’t fix the problem though. I found Request entity too large which suggested checking my setting for LimitRequestBody, but that wasn’t the problem either.
Eventually I found Bug 491763 – HTTPS+SSLVerifyClient require in <Directory>+big POST = Apache error which suggested I needed to apply the SSLRenegBufferSize directive which I did like this:
<Location /morpheus>
SSLVerifyClient require
SSLVerifyDepth 1
SSLRenegBufferSize 20971520
</Location>
And then after restarting Apache the problem was solved.
Had a read of RFC 2397 – The data URL scheme tonight. There’s a little more info on the data: URI scheme at Wikipedia.
Been learning about the Data URI scheme. That’s what you use to embed image data in HTML or CSS.
I’m always wondering how big I should make my database columns. I put together a simple PHP script which demonstrates the sizes of various strings which is handy as a reference when thinking about how big you should make your fields.