Chrome Version       : 49.0.2623.75 beta (64-bit)
URLs (if applicable) : (internal)
Other browsers tested: Firefox, Safari
  Add OK or FAIL, along with the version, after other browsers where you
have tested this issue:
     Safari: OK
    Firefox: OK
         IE: Not Tested

What steps will reproduce the problem?
(1) open https://www.myapps/files/test.txt/
(2) open https://www.myapps/files/test.txt

What is the expected result?
Contents of test.txt is displayed in browser window.

What happens instead?
HTTP server returns 404 indicating that it asked to process this URI: /files/test.txt/index.html

See this video for a demo of the problem: https://www.youtube.com/watch?v=-msN_U80RhY

Please provide any additional information below. Attach a screenshot if
possible.

OS X 10.8.5, all updates installed. I believe I run most recent Google Chrome version.

HTTP server is nginx. The problem is 100% reproducible but I'm not entirely sure how to trigger this behavior.

Anyway, Google Chrome apparently adds a forward slash to the end of /files/test.txt no matter how the URL is entered:

* either by entering it manually
* or by clicking https://www.myapp.com/files/test.txt link in a IM client

I think once it attempts to open /files/test.txt/ it seems to do that all the time afterwards. Not a problem in Safari or Firefox as those simply do not add the forward slash in my tests.

I think the key to reproducing this problem is to purposefully (in my case it was unintentionally) to first try to open an invalid URL that ends with forward slash. Then try to open a valid URL without the forward slash. I "broke" several test location URI's this way.