What is the reason Chrome resolves a double dot in a URI?

Today I came across an interesting behavior of Google Chrome.

Let's say that I have a web application that allows us to see user information:

http://app.com/user/Rok/info

Now suppose we have a user named ... When we visit his information page,

http://app.com/user/../info

you can see in the Developer Tools that the browser makes a request app.com/info.

Why does the browser do this? He must pass this solution to the server.

Recently, URIs are no longer directly attached to the file system. I was wondering if there is a specification aimed at this particular one.

+4
source share
1 answer
+4

All Articles