Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    text
    copied!<p>It's almost certainly a permissions issue, but probably not an IIS permissions issue.</p> <p>The functionality to redirect to the login page is an ASP .NET feature, which is configured in your Web.config file. It looks like you're using Forms authentication, so it'd be under:</p> <pre><code>&lt;configuration&gt; &lt;system.web&gt; &lt;authentication mode="Forms"&gt; &lt;forms loginurl="~/some-login-url"&gt; &lt;/authentication&gt; &lt;/system.web&gt; &lt;/configuration&gt; </code></pre> <p>Are you using any [Authorize] attributes (I'm not sure if those even exist in MVC 1)? Do you have any authorization entires in your Web.config?</p> <p>Does the first page display without requiring you to log in, and it's only when you are going to the second page that it's prompting you to log in?</p> <p>Another common problem that I've seen has to do with the App Pool recycling. I had an app once that would do a lot of work, store a lot of information in the user's session, and then the user would get sent to a sign-in page. I eventually figured out that the app was hitting its memory limits in IIS, causing it to recycle. Consequently, the user would be prompted to sign in again.</p> <p>I'm not sure if you might be having that exact problem, but have you looked at the Application Pool settings to verify that the app wouldn't be recycling? You might also want to make sure that you don't have any other really heavy applications in the same app pool that could also be recycling.</p>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload