Re: FW: php fastcgi
| From: | Nicolas Bérard-Nault | Date: | Wed, 13 Jun 2007 17:45:54 +0000 |
| Subject: | Re: FW: php fastcgi | ||
| References: | 1 2 3 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-30163@lists.php.net to get a copy of this message | ||
Returning 404 (or any other code other than 500) does not make sense. If an
user sees a Page not found error, he probably won't bother and won't come
back / delete his bookmark. On the other hand, if a search engine bot
stumbles upon one of these, the page is automatically erased from the index,
no questions asked. Off-hand, I can see these two consequences, on top of
not respecting the HTTP standard.
This seems obvious but am I missing something ?
On 6/13/07, David Coallier <davidc@php.net> wrote:
On 6/13/07, Stanislav Malyshev <stas@zend.com> wrote:-- Nicolas Bérard-Nault (nicobn@gmail.com) Étudiant D.E.C. Sciences, Lettres & Arts Cégep de Sherbrooke Homepage: http://nicobn.googlepages.comConfiguaratin option make sense, but PHP already has too manyconfigurationoptions especialliy for error reprting. I would like to avoid new ones.set_error_code(500) (or set_error_code(404)) might help? -- I am with set_error_code +1 Stanislav Malyshev, Zend Products Engineer stas@zend.com http://www.zend.com/ -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php -- David Coallier, Founder & Software Architect, Agora Production (http://agoraproduction.com) 51.42.06.70.18 -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php