10-Jul-2016

Server updated
Updated WASD server. As usual, it’s been a piece of cake, but this time there is a twist.
In the mapping file, I have a line:

if (client_connect_gt:10) pass * "503 Exceeding your concurrency limit!"

to prevent a single accessor to have more than 10 concurrent sessions – at least, this was my interpretation. But now it blocks ALL access, whether the number of sessions is higher than 10 or not, regardless the originating address. (apart from me, there seemed to be one more user, he got this message, but so did I – with ONE session… Since some parts of WASD are rewritten0, this may have slipped attention, so I reported it to Mark.

Once disabled, the site is accessable again.

This effects the non-secured sites only because the other ones don’t pass this mapping. However, I notices a weird thing using Firefox: The tile (“~”) used in accessing the user’s mail environment, translates to another character (‘not’ character) and therefore, Mozilla cannot be used to access the webmail-program directly – I have to get to the main page and invoke SoyMail from there.