Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I am using dotnetopenauth as an openid provider and have changed the Response.ApplyAppPathModifier file to a different file but the old one is always returned. The XRDS seems to be cached.
<URI><%=new Uri(Request.Url, Response.ApplyAppPathModifier("~/server.aspx"))%></URI>
Where is is cached?
Can I clear this?
Any help appreciated.
Thanks,
Graham
If I understand your question, your OP endpoint is at a different path than server.aspx, and you’ve changed your XRDS file to reflect this, but RPs are still attempting to connect at server.aspx. Is that right?
…assuming it is…
Your OP typically doesn’t cache this, but RPs often cache discover results for some period of time. It may just be that RPs haven’t noticed the change yet. You can try some OP tests at http://test-id.org, as any RP-side cache there has been disabled, to see if you got it right.
Another possibility is that your OP has two XRDS documents — one for user identity URLs and one for your OP identifier. Make sure you change both of them with your new OP endpoint.