Imported From: http://groups.google.com/group/in-portal-bugs/browse_thread/thread/58bad217609b40de#
In-Portal nice url caching system, that remembers what was parsed from url
and don't do parsing next time, but uses data from cache.
Cache reset also works fine.
Here is the scenario when cache could be misleading: 1.
- you have page http://www.website.com/directory.html with ID=2
...
- you have page that is shown, when a page isn't found (for 404 code)
...
- with ID=115
...
- visit directory page and witness that cache with ID=2 is created
...
- then rename directory page to directory2
...
- visit directory page (using old url) and witness that 404 page is
...
- displayed instead and cache is updated to reflect that (error logic here)
...
- rename directory2 to directory and visit directory page to see 404
...
- instead of correct page
I think that we shouldn't put url parsing result to cache, when not all url
was parsed correctly.
Related Tasks
--
Best Regards,
http://www.in-portal.com
http://www.alex-time.com
| Jira Legacy | ||||
|---|---|---|---|---|
|