问题
I have a Relying Party and a provider running with DotNetOpenAuth. The issue is that when the provider has not been accessed in a while it is unloaded from IIS to conserve memory (which is normally a good thing). However, in this case it causes the Relying Party to throw the "No OpenID endpoint found" exception.
I know that IIS can be configured to never unload an application, but that is not an option in this case.
Is there a way to increase the timeout on the relying party to let it wait until the provider "wakes up" and not throw the No OpenId Endpoint Found exception?.
I thought I had it with the "maxAuthenticationTime" property, but I guess this is really a setting for how many minutes in total the authentication round trip should be allowed to take.
Thanks.
回答1:
Yes, these timeouts can be configured via your web.config file. Below is a snippet, with the defaults which you can raise:
<messaging>
<untrustedWebRequest
timeout="00:00:10"
readWriteTimeout="00:00:01.500"
Full configuration options are documented.
来源:https://stackoverflow.com/questions/7904426/no-openid-endpoint-found-relying-party-timeout-option