Documentation on 'e' and 's' in execution=eXsY

[Jeff Chapin]

Thanks, I was guessing it was a loop -- and I think I even found what
causes it to end -- each time through the loop, they appear to be appending
more header information, until apache, which we are using as a reverse
proxy, finally chokes on it. Incidentally, it seems like cache/timeouts are
a factor in this. Thank you for validating my thoughts -- this gives me
enough to point fingers at the vendor and not let them point them back.

Jeff

On Thu, Feb 2, 2023 at 7:55 AM Cantor, Scott <cantor.2 at osu.edu> wrote:

> > I am looking for documentation on what the 'e' and the 's' in the string
> > 'execution=eXsY', found in various IDP URLs mean,
>
> They aren't somethiing to document, it's an internal detail of Spring
> WebFlow.
>  The entire parameter name and value are opaque, in an official sense, but
> there's probably some kind of description of them in the SWF documentation.
> What they are in the implementation is an execution/conversation number and
> a state number.
>
> > I have noticed that the URL typically contains something like
> execution=e78s1,
> > which seems relatively high, considering the values I see in the logs
> are usually
> > in the low single digits.....
>
> That's an SSO loop. Most loops these days are caused by the abomination of
> AJAX combined with a failure to deal with timeouts.
>
> -- Scott
>
>
>

-- 

Jeff Chapin,

Panther eSports Adviser
Systems/Applications Administrator
ITS-IS, University of Northern Iowa
Phone: 319-273-3162 Email: Jeff.Chapin at uni.edu
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://shibboleth.net/pipermail/users/attachments/20230202/6c37dddb/attachment.htm>