The following 168 words could not be found in the dictionary of 615 words (including 615 LocalSpellingWords) and are highlighted below:

about   action   address   again   all   allow   already   amount   an   and   Attach   bad   because   beyond   bit   bots   built   by   can   case   caused   Configuration   configured   continue   count   cpu   css   default   disk   doing   don   done   down   drink   dt   edit   engine   Especially   even   expected   File   for   fullsearch   gateway   get   gets   go   goes   got   guys   hammering   high   if   If   ignore   in   indexing   instead   interval   its   just   later   legitimate   less   limit   limits   load   lock   locked   lockout   log   logged   lots   make   makes   many   max   message   minute   mirroring   name   nasty   no   of   on   or   out   output   pages   pause   people   per   please   problems   process   protection   Protection   Proxy   proxy   put   quite   raw   rc   read   request   requests   rss   same   search   secs   see   server   should   show   single   slow   so   some   something   sometimes   spammers   start   stop   stuff   Surge   surge   tells   that   the   These   they   think   thinking   This   this   those   time   to   tracked   tracks   traffic   trash   trying   unusable   use   useless   user   users   using   usual   values   vandals   warn   warning   warnings   water   we   What   what   when   while   wikiconfig   will   without   won   You   you   your  


Surge Protection

Especially on an internet wiki sometimes the cpu and disk load gets quite high because the wiki has to process many requests. A high load makes the wiki slow or unusable for its legitimate users.

This is caused by:

  • some bad guys (spammers, vandals, ...) trying to put spam or trash on your pages
  • some less-bad guys (people just mirroring the wiki, without thinking about the load and the lots of useless requests and high traffic they make)

  • some bots, indexing the wiki content for some search engine

What can we do?

MoinMoin tracks requests by user name (if logged in) or IP address (if not logged in).

  • (!) Proxy or NAT users: please log in if surge protection tells you to slow down. This is because all people using the same proxy get tracked by that same, single IP. If you just log in, you won't have any problems even if you use the proxy / your NAT gateway.

If the request count goes beyond some configured limit in some configured time interval, it will start to warn you (you will see a surge protection warning message instead of the expected wiki output). If you see this warning, just read it and do what it tells.

You should stop doing those requests for a minute in that case (just read the stuff you already got, drink some water, ...). You will have no problems if you continue a while later (just slow down a bit, so you won't go beyond the limit again).

If you don't pause and ignore the warnings and the requests don't stop hammering the wiki server, the wiki will think you are doing something nasty and will lock you out for some configurable amount of time.


Configuration is done as usual: in your wikiconfig. These are the built-in default values:

    surge_action_limits = { # allow max. <count> <action> requests per <dt> secs
        # action: (count, dt)
        'show': (20, 60),
        'raw': (20, 40),  # some people use this for css
        'AttachFile': (60, 60),
        'diff': (30, 60),
        'fullsearch': (5, 60),
        'edit': (10, 120),
        'rss_rc': (1, 60),
        'default': (30, 60),
    surge_lockout_time = 3600 # secs you get locked out when you ignore warnings