jobeinabox/000-jobe.conf, line 17, 413 HTTP_REQUEST_ENTITY_TOO_LARGE

jobeinabox/000-jobe.conf, line 17, 413 HTTP_REQUEST_ENTITY_TOO_LARGE

by Constantine Zakkaroff -
Number of replies: 1
Hello All,

I'm tinkering with JobeInABox, and I have come across this, which I know :



I suspect this transpires because one of the support files is larger than Jobe's/Apache's HTTP LimitRequestBody is exceeded. There's also this in JobeInABox's code, on line 17:

Line 17

I've tried snooping around Apache's conf files, but for the life of me I can't find where this "TOO LARGE" setting would be.

Say, I want to play with an SQLite database file which is just under 100MB.

Anyone can point me to where this could be changed?

Kind regards,
Constantine


In reply to Constantine Zakkaroff

Re: jobeinabox/000-jobe.conf, line 17, 413 HTTP_REQUEST_ENTITY_TOO_LARGE

by Constantine Zakkaroff -

OK, to answer my own question... :)

Having done my homework, I've learned that php.ini has upload_max_filesize and post_max_size which control what can be uploaded/posted to Jobe. Then, having snooped around JobeInABox, I've confirmed that post_max_size is set to 10MB.

I wanted to play with a larger (question support file) SQLite database, say close to 100MB, so instead of messing with Jobe's PHP settings I split the support file into chunks, which are uploaded to Jobe one at a time, and then when the question answer is tested, the template code cats the chunks together and voila — we have our (zipped) .db file, which can then be unzipped.

This 100MB file is not critical, but I want to write some meaningful (and maybe, wickedly tricky) questions for this IMDB non-commercial dataset (https://developer.imdb.com/non-commercial-datasets/) which in full produces a ~10GB SQLite .db file, but I've created a trimmed down version (which zips to 97MB from 275MB) with millions of rows in it with most popular movies, tvSeries and people.

Just tinkering and exploring this marvelous tool. Thank you Richard!!!