"Replay detected of message" causes

[Cantor, Scott]

On 4/19/17, 7:59 PM, "users on behalf of Klingenstein, Nate" <users-bounces at shibboleth.net on behalf of nklingenstein at calstate.edu> wrote:

> Do you have reason to believe that disabling expiration checking alone would incur death by Webflow?

Getting an expired message implies requests arriving 5 minutes late or more. There's no way that's what's happening unless somebody's sitting on a hung browser for 5 minutes or more, and nobody would do that. It isn't doing what you think it is, and unless you're sitting with a user, you really have no idea what's really happening. You might see it in the log, but that isn't what the *user* sees. Normally they would either see it work and notice nothing at all, or be seeing the replay.
 
But this has nothing to do with what you disable or enable, if you send requests that don't match the flow's internal state it's not going to work. It thinks the client is at step 3 and the client resends a request for step 2. Or the conversation is expired altogether and the request comes in and just gets rejected, same as a back button does.

All you're talking about changing is the handling of one URL in the sequence from start to finish. Add in something like client storage or an actual login and you're looking at upwards of 6-7 URLs in the whole set, any one of which will cause the same problem if it's not handled properly or out of order or replayed or sent too late.

-- Scott