>> Could you please try to upgrade to slim/1.3.6-5.1 to see if that >> fixes your issue? > Of course, no problem, but it will have to wait a day or so.
I can now confirm that upgrading to 1.3.6-5.1 does indeed fix the issue I was experiencing. From my perspective that means that you may mark this bug as resolved, but you might want to tie it to to the 1.3.6-5.1 release some how. Thanks for being responsive and helpful! :) / Sebastian
