2011/11/8 Sławomir Skowron <szibis@xxxxxxxxx>: > Thank you very much. That's solve the problem. I was looking in source > code for that today, and i found i think self documented code for that > too :) > ... > > Theoreticaly, 100-continue is working with nginx, but i will dig this > soon. Now development can go on again. As I said before, haven't looked at nginx for quite a while now, so I'm not sure what's its status. When I looked at it a while back, it was sending 100-continue responses, but it did that unconditionally (when used with fastcgi), so we couldn't control the response timing. We had he same issue also with both apache and lighttpd. For apache we modified the fastcgi module so that we could actually control the 100-continue response. The specified configuration param should be set to true only when the modified apache module is being used. > > But, there is no info in changelog, or I miss something about rgw > cache capability, or maybe many more features, that can be useful in > any other ceph piece in future. > Yeah, we're a bit lacking on the documentation. We hope that'll be fixed soon. Yehuda -- To unsubscribe from this list: send the line "unsubscribe ceph-devel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
