-
Type:
Bug
-
Status: Closed
-
Resolution: Fixed
-
Affects Version/s: 6.0.12 EE, 6.2.10 EE GA1
-
Fix Version/s: 6.0.X EE, 6.1.X EE, 6.2.2 CE GA3 , 6.2.X EE, 7.0.0 M1
-
Component/s: Core Infrastructure
-
Branch Version/s:6.2.x, 6.1.x, 6.0.x
-
Backported to Branch:Committed
-
Story Points:7
-
Fix Priority:4
-
Git Pull Request:
- Set the following portal property: layout.friendly.url.page.not.found=/web/guest/home
- Deploy the attached test-404-hook-7.0.0.1.war
- access http://localhost:8080/web/guest/home
in the console you see the expected value: "responseStatus: 200"
- access http://localhost:8080/web/guest/home1
in the console you see the UNEXPECTED value: "responseStatus: 200"
If ETagFilter is turned off (com.liferay.portal.servlet.filters.etag.ETagFilter=true) or layout.friendly.url.page.not.found is not set, 404 is written to the log.
- relates
-
LPE-11759 ETagFilter intercepts the same request more than once
-
- Closed
-