Bug description:
When the chunksize variable in BioCrowd/app/config/webhook.php is set too high, the POST data from the webhook is truncated. This will result in vague errors such as: 500 internal server error.
Technical reason for bug:
Right now, it's not clear at what point the data is truncated, or by what program (nginx?).
Possible solution:
Set the chunksize to 1 (might not work when the response variable is too big).
Why make it possible to set it to more then 1?
There is a trade-off: the lower the chunk size, the slower the webhook script.
But:
When setting the chunk size way too high, nginx will cut off the data (cleanly) at some point and not all judgements will be processed, however no errors will be shown.
When setting the chunk size just a little too high, nginx will cut off the data (unclean cut). This will result in a 500 internal server error.
Bug description:
When the chunksize variable in BioCrowd/app/config/webhook.php is set too high, the POST data from the webhook is truncated. This will result in vague errors such as: 500 internal server error.
Technical reason for bug:
Right now, it's not clear at what point the data is truncated, or by what program (nginx?).
Possible solution:
Set the chunksize to 1 (might not work when the response variable is too big).
Why make it possible to set it to more then 1?
There is a trade-off: the lower the chunk size, the slower the webhook script.
But:
When setting the chunk size way too high, nginx will cut off the data (cleanly) at some point and not all judgements will be processed, however no errors will be shown.
When setting the chunk size just a little too high, nginx will cut off the data (unclean cut). This will result in a 500 internal server error.