Copied to clipboard

Flag this post as spam?

This post will be reported to the moderators as potential spam to be looked at


  • Andrew Knox 4 posts 27 karma points
    May 08, 2013 @ 12:16
    Andrew Knox
    0

    Redirect Loop - v1.2

    When the package is active using either templates or doc types, a match on certain pages will bounce back and forth between http and https?

    Looking at fiddler traffic, it's like it's finding a match when it's under http and then redirecting to https, then when its under https, it doesn't find a match and sends it onto http!

    This isn't happening for all pages mind, only for a recent page addition...

    I don't suppose anyone has any ideas regarding this? I'm using the latest version of the package, Umbraco v4.7.1.

    Regards
    Andrew

  • Lee Kelleher 3947 posts 15176 karma points MVP 10x admin c-trib
    May 08, 2013 @ 12:48
    Lee Kelleher
    0

    Hi Andrew,

    Thanks for reporting this.  Seems a strange one, as I haven't had any one report this issue for a while (since v1.0).

    Also interesting that a page will match on HTTP, but then not match against HTTPS.  Which type of redirect setting are you using? (e.g. DocType Alias, NodeId or Template)

    Thanks, Lee.

  • Andrew Knox 4 posts 27 karma points
    May 08, 2013 @ 13:04
    Andrew Knox
    0

    Thanks for the quick reply Lee, appreciated.

    Initially just for doc type, when that didn't work I tried it for template but the same thing happened.

    Thanks,
    Andrew 

  • Lee Kelleher 3947 posts 15176 karma points MVP 10x admin c-trib
    May 08, 2013 @ 13:08
    Lee Kelleher
    0

    Hi Andrew,

    Not sure if you're a developer - but if you want to take a look at the source-code, see if you think there is anything obvious that might be causing this redirect?

    Here's a link to the code that handles the redirect itself: https://bitbucket.org/vertino/https-redirect-for-umbraco/src/24b727fab891db54e558def6888dbd30408922c5/Our.Umbraco.HttpsRedirect/Events/ApplicationEventsHandler.cs?at=default

    I'll happily patch-up/release any fixes.

    Just seems strange that others are using this (in the wild) and aren't experiencing the same issue.  Wondering if it could be an IIS issue (e.g. classic pipeline vs integrated mode) - not sure though.

    Thanks, Lee.

  • Andrew Knox 4 posts 27 karma points
    May 08, 2013 @ 13:19
    Andrew Knox
    1

    Thanks again Lee, yep, I'd had a look before at the source in a .net decompiler to see what it was doing but nothing jumped out - what would be awesome if there was a debug mode where it would log the values out from the 3 Page object properties...

    • page.NodeTypeAlias
    • page.PageID
    • page.Template
    ... and if there was a match or not as it looks like it the Page object graph isn't being populated when under SSL. I've not got the time at present, though perhaps that's a little side project for myself when I do!
    Just that it doesn't make sense the way it works sometimes and not others, even when using the same template - only for a new page that I've created...
  • Laurence Gillian 597 posts 1214 karma points
    Dec 04, 2013 @ 13:31
    Laurence Gillian
    0

    I'm seeing this issue too with 2.0.0.

    The redirect is set to match one Document Type.

    The loop only occurs on certain pages, and is only happening in certain environments.

     >.< doh!
    
  • Laurence Gillian 597 posts 1214 karma points
    Dec 06, 2013 @ 13:23
    Laurence Gillian
    0

    We tracked it down, to an issue with the certificates not being correctly bond to the IIS Web Application.

  • shanem 39 posts 93 karma points
    Mar 28, 2014 @ 11:45
    shanem
    1

    Hello All

    I was having this exact same issue with v1.2.0, and spent some time looking at my IIS set-up and certificates and everything was correct but the redirect kept on happening. What was strange was it worked locally but not on my staging environment.

    My solution was to changes the host names set-up in Umbraco.

    On my local environment (that worked) I had this set-up in "Manage Host Names":

    sub.domain.local/en

    But on staging (that wasn't working) I had:

    http://sub.domain.com/en

    https://sub.domain.com/en

    So on staging I change this to:

    sub.domain.com/en

    This worked! So check your hosts names.

  • Amir Khan 1212 posts 2584 karma points
    Aug 13, 2014 @ 21:18
    Amir Khan
    0

    Shanem, your fixed worked for me as well. Looks like the mark as answer function is broken though in the forums?

Please Sign in or register to post replies

Write your reply to:

Draft