Feature request: compensate for server requested error pages
Reported by dleffler | January 29th, 2016 @ 02:19 PM | in 2.3.8 (closed)
Many/most managed servers tend to drop to a specific html page if they encounter a 403/404/500 error (forbidden.html, missing.html, internal_error.html) which will be added to our search query index (e.g., treated as a 'search' request instead of a 'not found'). We should add a new parameter to each of the site configuration error messages and option to enter the server requested page to handle it correctly.
Comments and changes to this ticket
-
expNinja January 29th, 2016 @ 02:25 PM
(from [08b2f2dbe7466c6720d6a8c747965daefce8711f]) Initial work for dealing with server error document requests [#1346] https://github.com/exponentcms/exponent-cms/commit/08b2f2dbe7466c67...
-
expNinja January 30th, 2016 @ 02:04 AM
- State changed from “new” to “resolved”
(from [6528cb8b78559790c2b5c3acf24b6ca091b24ce2]) Implement feature to not treat server requested error pages as search requests and add them to search queries, but route them appropriately [#1346 state:resolved] https://github.com/exponentcms/exponent-cms/commit/6528cb8b78559790...
Please Sign in or create a free account to add a new ticket.
With your very own profile, you can contribute to projects, track your activity, watch tickets, receive and update tickets through your email and much more.
Create new ticket
Create your profile
Help contribute to this project by taking a few moments to create your personal profile. Create your profile ยป
Bug Tracker for Exponent CMS
expNinja