Right then:

Records of requests for login_card with the specified client id, on the 20th July:

a) w2 at 13:31:14 from 84.65.95.133. No subsequent post.
b) w3 at 03:30:46 from 68.74.164.126. No subsequent post.
c) w3 at 14:34:41 from 195.188.176.200. Form posted 13 seconds later, redirect to search.jsp issued.
d) w3 at 14:41:31 from 195.188.176.200. Form posted 14 seconds later, redirect to "logn_card.jsp" issued. No idea where that mis-spelling comes from.
e) w3 at 15:08:08 from 195.188.176.200. No subsequent post.
f) w3 at 19:21:52 from 195.188.176.200. No subsequent post.
g) w3 at 21:05:24 from 213.122.22.252. No subsequent post.
h) w4 at 14:38:51 from 81.168.111.122. Form posted 15 seconds later, redirect to search.jsp issued. This is our office IP as the client.
i) w5 at 15:02:53 from 195.92.67.76. No subsequent post.

That makes 9 entrance attempts, one of which was from our own office IP. None of them returned a 500 error code (ie invoked the maintenance page).

If the client is running software which strips off the referral URL then form posts will not have been grabbed by the filter I ran above. Will follow through (f), as it's the example explicitly described in the error report.

T
- posted by Tim Bruce @ 3:01 PM