On Wed, Jan 9, 2013 at 5:19 AM, Ferenc Kovacs <[email protected]> wrote:

>
>
>
> On Thu, Sep 20, 2012 at 5:30 PM, Daniel Brown <[email protected]> wrote:
>
>> On Thu, Sep 20, 2012 at 7:30 AM, Ferenc Kovacs <[email protected]> wrote:
>> >
>> > so should I wait for them to go away (some? all?), or should I just
>> commit
>> > my patch knowing that it will not work on some of the mirrors?
>>
>>     No, just hold off for now.  I want to get them out first, so we
>> don't have more complaints coming in about broken things (in addition
>> to php.net/www.php.net.
>>
>> --
>> </Daniel P. Brown>
>> Network Infrastructure Manager
>> http://www.php.net/
>>
>
> hi,
>
> any update on this?
> currently we have the following mirrors without openssl support:
>
>    -
>    - md1.php.net
>    - jp1.php.net
>    - dk1.php.net
>    - pt2.php.net
>    - ru2.php.net
>    - es2.php.net
>    - in2.php.net
>    - mx2.php.net
>    - pa1.php.net
>    - tw1.php.net
>
> we could send out a notification to the php-mirrors list, that there is a
> new requirements, and give them a reasonable timeframe to fix up.
> btw. I've just heard from Googleguy that there are some mirrors where the
> posttohost is already broken, as they restrict external network access from
> php.
> I suppose that also should be listed as a requirement.
>

Yea, I opened a bug for this last month. I'm not sure what the best fix is
but this prevents users from being able to do things like add notes or vote
on notes from those mirrors that disable outgoing requests since all those
things depend on posttohost.

Here's the bug report.

https://bugs.php.net/63850


>
> --
> Ferenc Kovács
> @Tyr43l - http://tyrael.hu
>

Reply via email to