<div dir="ltr">The header that I removed for testing is:  <span class="gmail-s1" style="font-family:Menlo;font-size:11px;font-variant-ligatures:no-common-ligatures;color:rgb(46,174,187)">Header</span><span class="gmail-s2" style="font-family:Menlo;font-size:11px;font-variant-ligatures:no-common-ligatures;color:rgb(0,0,0)"> </span><span class="gmail-s3" style="color:rgb(180,36,25);font-family:Menlo;font-size:11px;font-variant-ligatures:no-common-ligatures">set</span><span class="gmail-s2" style="font-family:Menlo;font-size:11px;font-variant-ligatures:no-common-ligatures;color:rgb(0,0,0)"> Cache-Control </span><span class="gmail-s3" style="color:rgb(180,36,25);font-family:Menlo;font-size:11px;font-variant-ligatures:no-common-ligatures">"private, max-age=900" </span><div><span style="font-variant-ligatures:no-common-ligatures"><font color="#000000" face="arial, sans-serif">The apache version is 2.4.18. When that header is set in apache Web configuration under /etc/apache2/conf-enabled it will send me to the Stale Request. The logs in idp.process.log only show the same error as when the back button is used. </font></span></div><div><span style="font-variant-ligatures:no-common-ligatures"><font color="#000000" face="arial, sans-serif"><br></font></span></div><div><span style="font-variant-ligatures:no-common-ligatures"><font color="#000000" face="arial, sans-serif">How can I check for the IDP setting the header correctly to not cache? <br></font></span><p class="gmail-p1" style="margin:0px;font-variant-numeric:normal;font-variant-east-asian:normal;font-stretch:normal;font-size:11px;line-height:normal;font-family:Menlo;color:rgb(180,36,25)"><span class="gmail-s3" style="font-variant-ligatures:no-common-ligatures"><br></span></p><div><div dir="ltr" class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr"><div><p><span style="font-family:Arial,sans-serif;color:rgb(31,73,125)"><font size="1">Steve Herrera<br></font></span><span style="font-family:Arial,sans-serif;color:rgb(31,73,125)"><font size="1">System Administration<br>Information Security<br></font></span><span style="color:rgb(31,73,125);font-family:Arial,sans-serif;font-size:7.5pt">Bradley University<br></span><span style="color:rgb(31,73,125);font-family:Arial,sans-serif;font-size:7.5pt">Phone: 309 / 677-2336<br></span><span style="color:rgb(31,73,125);font-family:Arial,sans-serif;font-size:7.5pt">FAX: 309 / 677-3460<br></span><span style="font-size:7.5pt;font-family:Arial,sans-serif;color:rgb(31,73,125)">Email:  </span><u><span style="font-size:7.5pt;font-family:"Arial","sans-serif";color:blue"><a href="mailto:sherrera@fsmail.bradley.edu" target="_blank">sherrera@fsmail.bradley.edu</a></span></u></p></div></div></div></div><br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Tue, Nov 3, 2020 at 3:28 PM Cantor, Scott <<a href="mailto:cantor.2@osu.edu">cantor.2@osu.edu</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">On 11/3/20, 3:58 PM, "Steve Herrera" <<a href="mailto:sherrera@fsmail.bradley.edu" target="_blank">sherrera@fsmail.bradley.edu</a>> wrote:<br>
<br>
>    So what I found was one of our web headers was the issue. In apache, we had set our Cache-Control directive. As a test,<br>
> I removed it and it is working as expected. I will work on reducing that timeout.<br>
<br>
I'm not sure what you mean. The IdP should be setting the appropriate "by all means, don't cache this" headers to keep that from happening too much, though it can be a black art. There shouldn't be any sort of timeout, you absolutely can't cache anything the IdP returns with the exception of static material.<br>
<br>
-- Scott<br>
<br>
<br>
</blockquote></div>