What is the reasoning Chrome resolves double dot in URI?

Viewed 2729

Today I've came across an interesting Google Chrome behaviour.

Let's say that I have a web App that lets us see the information about the user:

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

Now let's assume we have an user named ... When we visit his information page,

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

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

Why is the browser doing that? It should pass this decision to the server.

Novadays, URIs are no longer directly bound to the filesystem. I was wondering whether there is a spec that targets this specific.

1 Answers
Related