ah, I didn't knew that, where can we set 403 pages template?
Configuration section location: "Configuration -> Website -> Advanced"
Setting name: "Template for "Insufficient Permissions" Error"
Below it is setting for 404 page.
not exactly. It's a "moved permanently" error message, with a link returned by server in Location field. see
rfc here
It avoid any page loss in search engines too.
I see no point in creating separate page, that nobody will see, since based on send 301 header automatic redirect will be made by web-browser.
about this task, it's not 302 error but 301.
10x, fixed in task.
My idea is not letting cache acting passively on results, but rather update it when we rename a page and save it. This way we could indicate in cache the 301 redirect and have a perfect moving message for users and search engines.
When we edit the page, we have all in hands to update cache if needed, and tell the system about new url, isn't it?
In-Portal uses a cache differently. Along with each cached url record a page ID in it is stored. When page is changed, then all cached urls, where it's found are deleted. When page will be visited by new url, then new cache pointing to same ID will be rebuild.
It's universal caching system, that doesn't know that page caches should be treated differently. Also if I'll implement what you've suggested, then there will be 2 cache records for 1 page:
- old url with 301 mark
- new url
and both record will point to the same id.
However idea to mark page renames in cache records seems interesting to me. That all stuff won't be working when mod-rewrite is off of course.
if there's another page by that name, we would have the same error message as now "page name must be unique" or page uri will be renamed if automatic filename is checked
It will happen as you say already, but because of it I will need to edit 2 pages instead of 1 (as now) to restore my page original url.
Isn't too much, it we act from the beginning, when we rename the page effectively?
I didn't get what you meant here.