[Framework-Team] Re: PLIP125 (link integrity) part II - redirect-on-move ready for merge
wichert at wiggy.net
Sun Dec 24 17:56:04 UTC 2006
Previously Hanno Schlichting wrote:
> Hi Martin,
> > The other performance hit (which is bigger) is on the
> > default_error_message page when it gets a NotFound error. In that case,
> > we attempt to do a redirect (more string and btree logic), and possibly
> > perform some traversal and catalog searches, in the first three methods
> > in this view:
> > http://svn.plone.org/svn/plone/plone.app.redirector/trunk/plone/app/redirector/browser.py
> > I don't see why the 404 page needs to be fast, though (except during the
> > spam attack we had on plone.org, but that's rather different).
> I'm mostly concerned about search engine crawlers revisiting already
> indexed sites. Not sure how much traffic those generate these days,
> though. Other than that the usual attacks websites have to endure come
> to my mind, like bots looking for insecure PHP apps on your domain (like
> awstats, phpmyadmin, ...). But probably you should filter those out in
> Apache or Squid in front of Plone anyways.
404 being slow has two problems: it is slow, and it is uncached which
makes it extra painful. Making it slower could be disastrous.
Wichert Akkerman <wichert at wiggy.net> It is simple to make things.
http://www.wiggy.net/ It is hard to make things simple.
More information about the Framework-Team