<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
On 4/19/2017 8:06 PM, Klingenstein, Nate wrote:<br>
<blockquote type="cite"
cite="mid:MWHPR01MB2222D23EC21CC006AC5A2543DE1B0@MWHPR01MB2222.prod.exchangelabs.com">
<p><span style="color:rgb(33,33,33); font-size:13.3333px">Failed HTTP requests and
resorting to the back button if they get a "this page couldn't
load" at some point. </span><span style="color:rgb(33,33,33);
font-size:13.3333px">It's specifically occurring only
on devices using cellular networks, some mobile providers have
spotty coverage here, and our users expect to be able to login
without human interaction in most situations. I think that
confluence of factors to be why I hear this so much now.</span></p>
<p><span style="color:rgb(33,33,33); font-size:13.3333px"><br>
</span></p>
<p><span style="color:rgb(33,33,33); font-size:13.3333px">Why do
people apparently get stuck consistently on this particular
check? I can think of several reasons, but initial DNS
resolution of the IdP combined with traffic prioritization by
the mobile carriers smells very suspicious to me.</span></p>
</blockquote>
<br>
How about rapid shifts between cellular IP service and one or more
wifi networks?<br>
<br>
(We currently have lots of people getting
NoSuchFlowExecutionException errors, because I forgot to add the
manual changes to treat them as StaleRequest during our 3.3.0
upgrade; apart from opening links in Office, a large number of them
seem to be caused by the client shifting IP addresses between
requests, which prevents our load balancer from properly "stickying"
them...)<br>
<br>
<pre class="moz-signature" cols="72">--
%% Christopher A. Bongaarts %% <a class="moz-txt-link-abbreviated" href="mailto:cab@umn.edu">cab@umn.edu</a> %%
%% OIT - Identity Management %% <a class="moz-txt-link-freetext" href="http://umn.edu/~cab">http://umn.edu/~cab</a> %%
%% University of Minnesota %% +1 (612) 625-1809 %%
</pre>
</body>
</html>