New required parameter added to WP_Http::processHeaders can cause warnings

[jshreve]

3.7 only bug (so does not involve stable)

I noticed that a new required parameter was added to WP_Http::processHeaders in [25044] by @dd32.

The problem is, if something was using this function (which is a public member) then you'll get a warning like:

Warning: Missing argument 2 for WP_Http::processHeaders()

I've since patched my code to pass the $url - but since this function has been around since 2.7 I'm guessing other code out there will hit that warning.

[dd32]

Indeed it should probably be marked optional if anyone else is using it

Curious though, Why/how are you using this method? It's only really public because of the architecture of WP_HTTP requires it to be a public method.

[jshreve]

Curious though, Why/how are you using this method? It's only really public because of the architecture of WP_HTTP requires it to be a public method.

I actually wasn't using it personally. The Jetpack server code uses it mixed with some CURL stuff and some signature writing stuff. It does it instead of straight WP_Http. The comment says "so it can do 'mulitpart/form-data requests". Again, that's all going based on comments in the source code :) - I was just fixing a warning I saw and figured someone else, somewhere might also be using the function.

[dd32]

In 25176:

WP_HTTP: Make the new 2nd parameter to WP_HTP::processHeaders() as optional. See #21182. Fixes #25179