-
Type: Bug Report
-
Status: Closed
-
Priority: Minor
-
Resolution: Fixed
-
Affects Version/s: None
-
Fix Version/s: 5.2.1-B2
-
Component/s: Url Processing
-
Labels:None
-
Change Log Group:Changed
-
Change Log Message:Failed rewrite listener now results in "404 - Page Not Found" during url parsing.
-
Story Points:1
-
Copy Issue Key:
-
Patch Instructions:
In-Portal has advanced mod-rewrite url processing/generation system, that allows:
- multiple units to be involved in url processing, where each unit is responsible for a specific url part parsing only;
- single unit is responsible for whole url parsing.
In either case unit must be able to tell (by looking at url) if url can be properly parsed or not. In case if unit can't parse the url a 404 error page must be displayed.
I recently discovered, that a unit can't say back, that 404 page should be shown in case if url itself ends up with a path to a template. For example:
- "/community_name/resource_type/resource_name.html" - shows page
- "/community_name/resource_type/resource_name/path/to/template.html" - shows page, but should show 404 error
- "/community_name/resource_type/resource_name/some/strange/stuff.html" - shows 404 error
- mentioned in
-
Page Loading...