DNN Redirect Loop - 310 Error

Discussion in 'Third-party applications' started by ferretstyle99, Aug 1, 2009.

Thread Status:
Threads that have been inactive for 5 years or longer are closed to further replies. Please start a new thread.
  1. In my staging environment, my DNN site works perfectly, pointing to my production discountasp.net-hosted db. When I deployed my site, I'm now receiving a "Error 310 (net::ERR_TOO_MANY_REDIRECTS): There were too many redirects." response.

    I can definitely see the page requesting itself over and over and over. Now, I know I cannot remotely debug due to discountasp.net policies, but was wondering if anyone else has encountered this and what I should investigate. Also wondering if there any way to access the IIS logs for my site so I can see what the requests look like.

    So far, I've just removed all portal alias entries other than my actual site.

    Thanks so much in advance for your help!
     
  2. i've found some details around this redirect.. http://www.codeproject.com/KB/aspnet/fix_dnn_redirect_loop.aspx

    essentially it points to AJAX Being the root cause. could you give the article a read and let me know if there's anything serverside that needs to change for this to be resolved?

    i've already
    1. pointed to version 3.5.0.0 of ajax everywhere in the web.config
    2. ensured that my portal aliases do not have a trailing "/"
    i've NOT
    1. implemented the "usePortNumber" node in the web.config.
    thanks again for a quick response. hopefully we can get this straightened out together!
     
  3. i found details on this one here: http://www.codeproject.com/KB/aspnet/fix_dnn_redirect_loop.aspx

    i've already ensured that all the bindings for ajax (system.web.services) have been updated in my web.config to point to version 3.5.0.0

    i've also verified that my portal alias does not have a trailing "/"

    after reading that article, do you see anything that could be required, server side, to relieve this problem?

    thanks!
     
  4. ...I think this is a DNN issue, honestly you should try posting in the DNN forums.
    Many of these DNN specific troubles are nearly impossible for us to diagnose.
    All the best,
    Mark
     
  5. In the codeproject article i linked above, there is mention to a line of code within PageBase.vb that handles problems related to AJAX. The line of code handles issues related to Medium trust with AJAX. I modified my web.config to enable full trust and now my site loads just fine.

    Now, I don't want to run this site in full trust, as I am guessing this is not a good practice.

    I stumbled upon this next thread in which there is an indirect method for setting up custom trust levels for individual subsites.

    Any idea why I would need to increase trust in order for my site to work (specifically with regard to AJAX)?

    Thanks in advance!
     
  6. I dont know enough about the inner workings to tell you specifically why it needs full trust - but I can tell you a lot of things do and more often than not - you want to run in full trust.

    We are one of the rare hosts that even allow this so we have a lot of customers that select us for that reason. Point being most sites are running in full trust.
     
  7. Thanks Chuck! I do appreciate the discountasp.net staff. You guys always get back to your customers, which is why I continue to be one! Here are my findings.

    After even FURTHER research, it seems that this may be the situation please do comment with your thoughts / facts here..

    If System.Web.Extensions.dll(AJAX) is GAC'd, then you can run under medium trust.
    If System.Web.Extensions.dll(AJAX) is in the site's Bin directory, then you must have full trust to the app can reflect on that assembly to access the ajax features.

    How did I come to this conclusion?
    I updated my web.config to have trust="Medium"
    I renamed System.Web.Extensions.dll to System.Web.Extensions.dll.exclude on the server

    The site then ran correctly.
     
Thread Status:
Threads that have been inactive for 5 years or longer are closed to further replies. Please start a new thread.

Share This Page