[ACE-5366] Wrong URL makes RM site to be displayed in a wrong way Created: 10-May-16 Updated: 11-May-16 Resolved: 11-May-16
|Status:||Ready to Test|
|Project:||Alfresco One Platform|
|Reporter:||Oana Nechiforescu [X] (Inactive)||Assignee:||Web Apps (Inactive)|
|Remaining Estimate:||Not Specified|
|Time Spent:||Not Specified|
|Original Estimate:||Not Specified|
Alfresco 5.1 build #19 https://releases.alfresco.com/Enterprise-5.1/5.1.0/AlfrescoOne/build-00019/ALL/, RM 2.5 enterprise build #460
|Attachments:||another container icon.png whole File Plan in folder.png wrong page.png|
Steps to reproduce:
1. Create RM site.
3. Create a category c1, a folder f1 inside. Navigate inside folder f1. The URL would be on Firefox : [http://localhost:8080/share/page/site/rm/documentlibrary#filter=path|%2Fc1%2Ff1&page=1] . Delete everything that is after the folder name in the URL, so after "f1" part and write "%2F" instead. Access the resulting URL [http://localhost:8080/share/page/site/rm/documentlibrary#filter=path|%2Fc1%2Ff1%2F] .
4. Create a category c1, a folder f1 inside. Navigate inside folder f1. The URL would be on Chrome : http://localhost:8080/share/page/site/rm/documentlibrary#filter=path%7C%2Fc1%2Ff1%7C&page=1 . Remove the "%7C" part and access the resulting URL http://localhost:8080/share/page/site/rm/documentlibrary#filter=path%2Fc1%2Ff1&page=1.
Expected results for 2), 3), 4):
File Plan is displayed with an error that the URL is invalid or just display whole File Plan and get redirected to a valid URL like http://localhost:8080/share/page/site/rm/documentlibrary.
Actual results for 2):
Actual results for 3):
Actual results for 4):
All the above are reproducible on all browsers when accessing the direct resulting links.
Please check for other cases as well when invalid URLs can be accessed and how we could approach displaying the resulting error page.
|Comment by Christine Thompson [X] (Inactive) [ 11-May-16 ]|
We believe that this is a Core issue so moving over to ACE.
|Comment by Kevin Roast [X] (Inactive) [ 11-May-16 ]|
This is not a use case we would expect to work or a user to do in standard operation of the application.
This area (URL encoding and Path handling generally in Share and URLRewrite JAR) is non-trivial, has NO unit tests and is extremely sensitive to regressions (several this year already). We will not be attempting to fix this issue due the complexity and high likelihood of regression to other areas of Share doclib in doing so.