Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:51557 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 6124 invoked from network); 3 Mar 2011 09:34:17 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 3 Mar 2011 09:34:17 -0000 Authentication-Results: pb1.pair.com smtp.mail=mozo@mozo.jp; spf=permerror; sender-id=permerror Authentication-Results: pb1.pair.com header.from=mozo@mozo.jp; sender-id=permerror Received-SPF: error (pb1.pair.com: domain mozo.jp from 209.85.161.42 cause and error) X-PHP-List-Original-Sender: mozo@mozo.jp X-Host-Fingerprint: 209.85.161.42 mail-fx0-f42.google.com Received: from [209.85.161.42] ([209.85.161.42:54468] helo=mail-fx0-f42.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 03/A1-30734-5906F6D4 for ; Thu, 03 Mar 2011 04:34:15 -0500 Received: by fxm20 with SMTP id 20so866628fxm.29 for ; Thu, 03 Mar 2011 01:34:11 -0800 (PST) Received: by 10.223.86.140 with SMTP id s12mr1149151fal.145.1299144851274; Thu, 03 Mar 2011 01:34:11 -0800 (PST) MIME-Version: 1.0 Received: by 10.223.73.202 with HTTP; Thu, 3 Mar 2011 01:33:50 -0800 (PST) In-Reply-To: References: Date: Thu, 3 Mar 2011 18:33:50 +0900 Message-ID: To: Alexey Zakhlestin Cc: internals Mailing List Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable Subject: Re: [PHP-DEV] RFC: built-in web server in CLI. From: mozo@mozo.jp (Moriyoshi Koizumi) Hi, On Thu, Mar 3, 2011 at 3:35 PM, Alexey Zakhlestin wrot= e: > On Wed, Mar 2, 2011 at 11:55 PM, Moriyoshi Koizumi wrote: >> Hi, >> >> Just to let you know that I wrote a RFC about built-in web server >> feature with which PHP can serve contents without a help of web >> servers. =A0That would be handy for development purpose. >> >> If interested, have a look at http://wiki.php.net/rfc/builtinwebserver . > > Interesting, indeed. > > I noticed, that you hardcode mimetypes and index_files. > Mimetypes can probably be obtained from the system =97 we even had some > extension doing that. > And index_files should be configurable, because there are some > situations when people don't want any mime-types at all. > > Also, it would be good to be able to configure which files are > actually parsed by php, not just served. Currently, these are only > ".php" files > We coundn't always count on the existence of mime.types, which is likely installed with Apache that is uncalled for. Neither do I see any good reason to make index files configurable because I have hardly seen such a peculiar setting for several years that uses file names other than index.html or index.php for index files. I used to use index.htm for technical reasons though. In short, if you need to configure it more, it'd be better off installing Apache to do the right job. I would like to cover just a marginal part of the developer needs with this. Regards, Moriyoshi > -- > Alexey Zakhlestin, http://twitter.com/jimi_dini > http://www.milkfarmsoft.com/ >