Re: allow_url_fopen should be INI_ALL
| From: | Andi Gutmans | Date: | Thu, 30 Jun 2005 05:06:43 +0000 |
| Subject: | Re: allow_url_fopen should be INI_ALL | ||
| References: | 1 2 3 4 5 6 7 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-17029@lists.php.net to get a copy of this message | ||
Russell,
We got the point. Now please let internals@ continue to be productive and focus on PHP development.
Sorry to be blunt but this thread is getting old and preventing us from being productive.
Thanks,
Andi
At 12:58 AM 6/30/2005 -0400, Russell Nelson wrote:
Etienne Kneuss writes: Russell Nelson wrote:And you're trying to tell me that PHP's 'include' doesn't have aproblem??The problem is not located on include, the problem is more general : "trusting user's data" That's *also* a problem. Include's problem is a different one: that no other language allows you to include code located on another machine. You can't argue that an experienced programmer will not trust user's data AND argue that an experienced programmer will realize that 'include' happily fetches remote code, when in the experience of said programmer no other languge's 'include' does that. PHP's 'include' surprises people. That's evidence of a design error. ----My blog is at blog.russnelson.com | If you want to findCrynwr sells support for free software | PGPok | injustice in economic521 Pleasant Valley Rd. | +1 315-323-1241 | affairs, look for the Potsdam, NY 13676-3213 | | hand of a legislator.-- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php