Thanks for your pull request. It looks like this may be your first contribution to a Google open source project (if not, look below for help). Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

📝 Please visit https://cla.developers.google.com/ to sign.

Once you've signed (or fixed any issues), please reply here (e.g. I signed it!) and we'll verify it.

What to do if you already signed the CLA

Individual signers

• It's possible we don't have your GitHub username or you're using a different email address on your commit. Check your existing CLA data and verify that your email is set on your git commits.

Corporate signers

• Your company has a Point of Contact who decides which employees are authorized to participate. Ask your POC to be added to the group of authorized contributors. If you don't know who your Point of Contact is, direct the Google project maintainer to go/cla#troubleshoot (Public version).
• The email used to register you as an authorized contributor must be the email used for the Git commit. Check your existing CLA data and verify that your email is set on your git commits.
• The email used to register you as an authorized contributor must also be attached to your GitHub account.

The memory leak was already fixed in #114 - you should not observe it if you use a SNAPSHOT build of Volley, and we'll release the fix in upcoming version 1.1.1.

Otherwise, this change seems to consist of a parameter to HurlStack that, when set, calls setChunkedStreamingMode(0) when creating the HttpUrlConnection. I don't know what the value is of doing this in general - perhaps you could provide more details if you think this is truly something that other apps would benefit from. But if it's just for your own use case, I'd recommend you just extend HurlStack and override createConnection, and you can do whatever you want to the connection before returning it there. Then no change is needed to Volley.

Closing this out, but let me know if you still think there is something generally useful here. In the future, I'd recommend reaching out to [email protected] or filing a bug first before making a change - we can generally help advise on the right direction before you get to writing any code.