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.

<div id="title">
	<div id="date">###SINCE### - ###TO###</div>
	<div id="roomjid">###JID###</div>
	<div id="links">(join via <a class="component" href="xmpp:###JID###?join">client</a>)</div>
</div>
<div id="calendar">
	<div id="navigation">
		<a class="nav" href="../###PREVIOUS_ROOM###/">&lt;</a>
		<a class="nav" href="../">^</a>
		<a class="nav" href="../###NEXT_ROOM###/">&gt;</a>
	</div>
	<div class="weekday">List of rooms for this component</div>
	<div id="roomList">###ROOMS###</div>
</div>
<div class="topic">###ROOMTOPIC###</div>
<div id="main">
###DAYS_STUFF###
</div>