Description: ------------ A new E_STRICT-compatible version of HTTP_Request package [1] has been released, please consider using it instead of the old HTTP_Request. If HTTP_Request2 is not yet ready for your package's needs, do not hesitate to open requests for missing features. [1] http://pear.php.net/package/HTTP_Request2/

Any update on this?

Sorry, I don't know why I haven't responded in this bug report. AFAIR I have been in contact with the reporter, but I may be wrong. Anyway ... I am reluctant about adding a dependency on a non-stable package. But as long as this package itself is unstable, it may not be a big problem, as long as it specifies exactly what version of the HTTP_Request2 it supports.

HTTP_Request2 obviously cannot be declared stable before its dependencies, namely Net_URL2. Coincidentally, the latter is maintained by Christian Schmidt, you probably know that guy. :) That being said, I doubt that API of HTTP_Request2 will change a lot. You can add a dependency on >= 0.4.0 and < 0.5.0 if you want to be safe, a few minor BC breaks related to request body handling may be possible in 0.5.0

Any progress on this? I see there's nothing in SVN. HTTP_Request2 support would make it possible to support updating an object's metadata without having to re-upload the whole file. HTTP_Request doesn't support sending the content-type header with an empty request body as required by the S3 Object::COPY method.

This bug has been fixed in SVN. If this was a documentation problem, the fix will appear on pear.php.net by the end of next Sunday (CET). If this was a problem with the pear.php.net website, the change should be live shortly. Otherwise, the fix will appear in the package's next release. Thank you for the report and for helping us make PEAR better. Fixed in [290941].