Bug #61286 [Com]: If the trailing path that follows a script contains a dot PATH_INFO is not set

From: Date: Fri, 18 Nov 2016 21:31:42 +0000
Subject: Bug #61286 [Com]: If the trailing path that follows a script contains a dot PATH_INFO is not set
References: 1  Groups: php.bugs 
Request: Send a blank email to php-bugs+get-205467@lists.php.net to get a copy of this message
Edit report at https://bugs.php.net/bug.php?id=61286&edit=1 ID: 61286 Comment by: drakej at drakej dot com Reported by: galacticvoid+php at gmail dot com Summary: If the trailing path that follows a script contains a dot PATH_INFO is not set Status: Wont fix Type: Bug Package: Built-in web server Operating System: OSX PHP Version: 5.4.0 Assigned To: laruence Block user comment: N Private report: N New Comment: Yet another reason to never use PHP. We introduced a feature to aid in development. OK awesome, projects start using it as well. You should test using this new development feature. Awesome, oh wait within 10 minutes, you find out it can't handle something every other web server can. Oh but it won't be fixed because it's not intended to be production. OK but nobody ever said it was, they just want to work for TESTING and DEVELOPMENT. Don't mind that it doesn't, because it does what our internal team wants it to do, which is good enough. F you, I got mine, so won't fix. Great because I got a multitude of other options besides PHP which solve the job, usually better as well. So I got mine too, plus I got more fodder to show people why PHP is never a good decision. Previous Comments: ------------------------------------------------------------------------ [2016-05-25 19:40:57] lotyrin at gmail dot com I don't intend for the PHP internal server to have any additional features, however I do expect its existing features to function regardless of if my routes contain a dot. I haven't made the mistake of placing the PHP internal server into production use, just perhaps the mistake of placing it into use at all. ------------------------------------------------------------------------ [2016-03-30 20:22:33] krakjoe@php.net The internals team have no interest in developing a fully featured, production ready web server. The CLI web server is only a development server, it does what is necessary for us to run tests, and you can use it for some testing. Any product that decides to deploy the CLI server as if it were a production ready server is doing so mistakenly. ------------------------------------------------------------------------ [2016-03-30 15:58:48] contato at nemostein dot com dot br This doesn't make any sense... What is the point of letting the router run but not filling the data correctly?! The router become useless in so many situations because of this. ------------------------------------------------------------------------ [2016-01-02 03:06:59] dusan dot maliarik at gmail dot com Here https://github.com/getgrav/grav-plugin-admin/issues/3 apparently there are apps that are forced to include special case for the built-in web server, because it doesn't behave like expected. That kind of counters the goal of it, right? ------------------------------------------------------------------------ [2016-01-02 03:05:17] dusan dot maliarik at gmail dot com Dear @laruence, this is non-sense. If you allow it to be routed to the script, but you don't set the PATH_INFO key to what is expected, then that's surely a bug that deserves fixing. If the script returns 404, go ahead, serve the static file. ------------------------------------------------------------------------ The remainder of the comments for this report are too long. To view the rest of the comments, please view the bug report online at https://bugs.php.net/bug.php?id=61286 -- Edit this bug report at https://bugs.php.net/bug.php?id=61286&edit=1

« previous php.bugs (#205467) next »