These paths have to be resolved b the browser, not PHP as server. Browsers interpret relative URLs relative to the current URL ...

"Browsers interpret relative URLs relative to the current URL ..."

The current URL is "http://localhost:90/updater" not "http://localhost:90/".
On the screenshot you see, that i get a http code 200 for browsing into the subdir. Then <link href="assets/css/bootstrap.css" rel="stylesheet"> should resolve to http://localhost:90/updater/assets/css/bootstrap.css, but it's requested as http://localhost:90/assets/css/bootstrap.css - logged as "/assets/css/bootstrap.css" - the file is at /updater/assets/css/bootstrap.css.

Putting http://localhost:90/updater in front of the href works, but thats not what i want to use, because the page is served with Nginx. And that works...

When you browse '/application', the web browser has no way of knowing that 'application' is a directory. It looks like a file in '/'. Consequently, the base URI is '/', so the browser requests resources relative to there. The correct path you should be viewing from is '/application/'. Therefore, it's a web server's responsibility, whenever a directory is requested without a trailing slash, to send a redirect so that it does have a trailing slash. Apparently this vital redirect isn't being sent. I'm not familiar with PHP's built-in web server so I can't say if this missing redirect is a bug in the server or a configuration or user error.

Demo: https://www.dropbox.com/s/go5ikn4kvryl6e1/php-server-bug.zip

http://localhost:90/application    <-- not working
http://localhost:90/application/   <-- working

Anon, i think you might be right and an implicit redirect would solve this.

I can confirm this. Doesn't happen with Apache or Nginx, but visiting a page without the trailing slash causes subsequent links to fail.

I can confirm this too. There is even a post of mine in Stack Overflow (http://stackoverflow.com/questions/25095425/php-built-in-webserver-and-relative-paths) detailing a whole scenario mainly based in relative paths that does not work as expected.

And it's not only with this application I developed. phpMyAdmin also relies on relative paths to load their CSS and JS and the "." is being resolved as one level above, right after the port definition, instead of the current accessed by browser.

I can confirm this problem is real for relative links...

Same app tested with several other Server IIS5/IIS6/IIS7 and Apache works ok...

PHP internal server is trying to find the resource indicated by the relative path always in the parent folder...

try also with './*' prefix, no prefix, only works with absolute path... and this is very annoying... please fix (php 5.3x)

I'd hate to say '+1', but this bug is still set to status 'not a bug'. I am experiencing the same problem with PHP 5.6.

Please take another look at the ticket description and at useful comments that were added since it was marked as 'not a bug'.

Thanks!

This is definitely a bug but still marked as "Not a bug" and not fixed as of PHP 5.6.30 .

As said the relative handling comes from the client. But there is indeed a bug:

On a "GET application" the server has to do a redirect (304?) to "application/" in case this is a directory.

Right, the redirect is not triggered, what has been requested as
request #67027.  I'm closing this ticket as duplicate.