mod_sasl2_fast: Fix harmless off-by-one error (invalidates existing tokens!) Problem: This was causing the key to become "<token>--cur" instead of the expected "<token>-cur". As the same key was used by the code to both set and get, it still worked. Rationale for change: Although it worked, it's unintended, inconsistent and messy. It increases the chances of future bugs due to the unexpected format. Side-effects of change: Existing '--cur' entries will not be checked after this change, and therefore existing FAST clients will fail to authenticate until they attempt password auth and obtain a new FAST token. Existing '--cur' entries in storage will not be cleaned up by this commit, but this is considered a minor issue, and okay for the relatively few FAST deployments.

body {
  margin: 0
}

a {
  color: #0000FF
}

ul {
  margin: 0
}

.btn {
  margin-right: 0.3em
}

.btn:last {
  margin-right: 0
}

#main {
  padding: 10px
}

#main div {
  margin-left: 14px
}

#main p {
  margin-left: 14px
}

#top {
  clear: both;
  width: 100%;
  padding: 0;
}

#header {
  height: 172px;
  background: url(../images/tile.png) repeat-x
}