TYPO3 Core

To test, run linkvalidator task with check for an external HTTP site (e.g. on Introduction package).

Is a duplicate of #37085. However, in this other issue there are patches for branches 4-6 and 4-7, which also need to be fixed.

Both solutions work, either moving the included files or changing the path in CookieJar. However, the fix that was applied to original PEAR has both. See http://svn.php.net/viewvc?view=revision&revision=318430 and http://svn.php.net/viewvc?view=revision&revision=318432 (only the change to CookieJar should be important here). So, one could also completely update to HTTP_Request2 2.1.1 - IMO this would be the best solution.

Yes, an update would be best ... IMHO we could update even in lower branches, because the API is stable.

? This issue, of which the number is 41295, is closed "in favor of issue #41295" ? Something seems to be wrong here!

Or do you mean #32387 instead since this refers to the same bug but is still open?

Anyway: I replaced in my live TYPO3 4.7 the PEAR package HTTP_Request2 with latest version 2.1.1 and PEAR package Net_URL2 with latest version 2.0.0. Works fine.

I could create a patch for 4.6, 4.7 and 6.0, but we should decide first to which issue it should be attached.

@Daniel Hinderink it would be cool if you could create a patch for the update. Just use this issue number.

Daniel Minder wrote:

Anyway: I replaced in my live TYPO3 4.7 the PEAR package HTTP_Request2 with latest version 2.1.1 and PEAR package Net_URL2 with latest version 2.0.0. Works fine.

I could create a patch for 4.6, 4.7 and 6.0, but we should decide first to which issue it should be attached.

Philipp Gampe wrote:

@Daniel Hinderink it would be cool if you could create a patch for the update. Just use this issue number.

This is still a problem with the current TYPO3 6.0.4. What's the status here? Don't know why this ticket is closed...

I just create task #48027 for this issue and pushed patches for 4.7, 6.0, 6.1 and master.

Please only push to master (or highest effected branch). Backports, including all patchsets, will be done by committer. It is too easy to miss a change done in a patchset if you push to other branches beforehand. Additionally, cherry-picking is easier than.