Too many redirects using i18n.UrlLocalizationScheme.Scheme2 (ERR_TOO_MANY_REDIRECTS)

[rafaeldruiz]

The default language is "en" (default of i18n).

Using i18n.UrlLocalizationScheme.Scheme1 (default of i18n) everything works fine. All languages not configured are redirected to "localhost/en":

• "localhost/en" (ok)
• "localhost/es": redirected to "localhost/en" (ok)
• "localhost/en-US": redirected to "localhost/en" (ok)

Using i18n.UrlLocalizationScheme.Scheme2 to hide the default schema, the browser shows the error "Too many redirects" (ERR_TOO_MANY_REDIRECTS) with the same scenarios.

• "localhost/en" (ok)
• "localhost/es": error
• "localhost/en-US": error

What can be done to fix this issue?

Thanks, Rafael.

[turquoiseowl]

With Scheme2, is "localhost/en" being redirected to "localhost/" ?

What versions of i18n and ASP.NET are you using?

[rafaeldruiz]

Schema1:

• "localhost/": redirected to "localhost/en" (ok)
• "localhost/en": continued "localhost/en" (ok)

Schema2:

• "localhost/": continued "localhost/" (ok)
• "localhost/en": continued "localhost/en" (not redirected to "localhost/" but works)

Versions:

• i18n: 2.1.4.0 (installed from nuget)
• ASP.NET MVC: 5.2.3

[turquoiseowl]

I'm presuming that is ASP.NET 4.5 under MVC? That should work fine. I just want to rule out a new version of ASP.NET causing a problem.

Have you tried clearing browser cache between change of schemes (Ctrl-F5)? And different browsers?

Can you provide the http responses for, say, "localhost/en-US" (Scheme2).

This is quite a common problem I've had when setting up a site. In debug builds there should be Debug trace output to help diagnose the redirects. If you fancy building and referencing the source, the EarlyUrlLocalizer.ProcessIncoming method is a good starting point with redirects.

[rafaeldruiz]

Yes, it's ASP.NET 4.5.

All browsers have the same result:

• Windows 8.1: Chrome and IE
• Mac OS: Chrome, Firefox and Safari.

[turquoiseowl]

Please provide the initial http GET request including headers, the initial GET response including headers, then the same for the next request/response i.e. the one that loops.

[rafaeldruiz]

• 1st http get request:

Remote Address:[::1]:2699 Request URL:http://localhost:2699/en-us/sites/10001 Request Method:GET Status Code:302 Moved Temporarily Response Headers view source Content-Length:0 Date:Thu, 05 Nov 2015 17:02:23 GMT Location:/en-us/sites/10001 Server:Microsoft-IIS/8.0 X-Powered-By:ASP.NET X-SourceFiles:=?UTF-8?B?WTpcRG9jdW1lbnRzXE15UHJvamVjdHNcTGVhZEdyaWRcc291cmNlXFVJXFVJVXNlclxlbi11c1xzaXRlc1wxMDAwMQ==?= Request Headers view source Accept:text/html,application/xhtml+xml,application/xml;q=0.9,image/webp,/;q=0.8 Accept-Encoding:gzip, deflate, sdch Accept-Language:en-US,en;q=0.8 Cache-Control:max-age=0 Connection:keep-alive Cookie:_hjUserId=7fedb156-fbc6-4f42-ac1b-dcc2314bc1c8; current-lang=en-US; ASP.NET_SessionId=vxx0wur3rhdxe2qryzvh5o2j; __RequestVerificationToken=KqAevXKp4glW_AyMue6xwJTAHDE2DTBKngSdzH79XNP-NXBBblGoygcMnPBgV8BuUlNwjnI_kfwGZ_Bn8lEJn8Lg2GO8nePuQoLDlP2x2vM1; .AspNet.ApplicationCookie=cP7Yxf5Ik66DL7q2XFK9djM1AUSfZ39RREdRY0-Qw4aO9Nawpq0UdBg9xZGJJEx0ksCEHpOY7bjXgcKGrY88UBw6xuUgwRds86-VAOxH0FlFNUzvd6EhQtfZHmtY1KiJrnp99Tqqbyx0ik6EsUpozNkHz_VpK-8GJpcqJLixnW2Nbg9O0AjkLiV-OXz1Zn2GGu8xhY41PWBJTlNpJt-iIvW-GZcwsMwq9xUho3w9cq-aMwd_rKj6X4kgb0NN6Ika8wL8IP_nEfHpWMWeBSMGjdjQgw-QUXi_25oVgTe1KCj2aEMM7czii7nL8PLxnxcRi-USFNHdwK5cmRRNgyl_kE38NjBGgMaRPXivdf2zlJNNcFxs4MK83JI-tBqLChUjXMc83l-6xkg8AJL1R9_H_dilBb7EK6n3fVQyhiBm_yUPGfQsOFq-3QgeiXCpaA-9e8t6vyl1iCoJDkQqgwM2cW885hAv9wnlP54MxxL-mn--hGyv_nHQHULH8ytQo07N Host:localhost:2699 Upgrade-Insecure-Requests:1 User-Agent:Mozilla/5.0 (Windows NT 6.3; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/46.0.2490.80 Safari/537.36

• 1st http get response: "Failed to load response data"
• 2nd http get request: Remote Address:[::1]:2699 Request URL:http://localhost:2699/en-us/sites/10001 Request Method:GET Status Code:302 Moved Temporarily Response Headers view source Content-Length:0 Date:Thu, 05 Nov 2015 17:05:57 GMT Location:/en-us/sites/10001 Server:Microsoft-IIS/8.0 X-Powered-By:ASP.NET X-SourceFiles:=?UTF-8?B?WTpcRG9jdW1lbnRzXE15UHJvamVjdHNcTGVhZEdyaWRcc291cmNlXFVJXFVJVXNlclxlbi11c1xzaXRlc1wxMDAwMQ==?= Request Headers view source Accept:text/html,application/xhtml+xml,application/xml;q=0.9,image/webp,/;q=0.8 Accept-Encoding:gzip, deflate, sdch Accept-Language:en-US,en;q=0.8 Cache-Control:max-age=0 Connection:keep-alive Cookie:ASP.NET_SessionId=dglsiwlx3entcwekowyvqueg; __RequestVerificationToken=uTTRdcVn835nRFqzSXyNDGZo58JDCyYPPTpZPPp-P-YGuM59Ncos82uaxlPS2SMXTVzjfvIksjJcy-ksP_uvVx3d2viDDO-DGMtJb4Ojr9o1; .AspNet.ApplicationCookie=q6WyeEtoj0_jZdzlTtx11QF9-iSBMtT_kgv2YAItexzTNBEJjyETz7zAZ8ZklEmSvBQNpp4KYwZjRW6mlsFtqO0KSV2_Wog10DFtz2b52pmQtA2Qt9NzVTb-rd28_Iz_60wlG3CsEzjiWiCw4ZsTvdvx63cPFG4rCN_kNO0CVuu5NCitdT3Hv3GMwbBHBH41GYv0wd9uU5c8vITFNPTOH3DYBuqYSquoI563wi6vQ3ad2pQJvc_Z7Qht4T2XVYZdZOylFOpPX2aaqZ7jTkNC61mB_f_CqHxIVAmYQeD5x-DIy55e2tTIf26G2-AFDEwF9kUZ2KK4qniGcCcsay8uegYTlwLOdgLCL8-j9CeB6zEpPf_rcsd5agq3YNLnsS64liyTWkmVYGonCtoMexnd8keNilZNj3e6nEuBMoDNtxfMOxZ24KUohJ2HJrJ9ldAmPrivj8pnstW1eW9zx4PK67HhMMnX-PkcSvuFg4iU8zVdXBVVQ49-35dvoeEPkmv0 Host:localhost:2699 Upgrade-Insecure-Requests:1 User-Agent:Mozilla/5.0 (Windows NT 6.3; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/46.0.2490.80 Safari/537.36
• 2nd http get response: "Failed to load response data"

[turquoiseowl]

I've pushed what is hopefully a fix for this. It would help me a lot if you would test with a clone of this repo before I submit a new NuGet package. Thanks.

[turquoiseowl]

Note to self: A potential gotcha when swapping between Scheme1 and 2 during dev is that browsers can remember permanent redirects, so it is a good idea to flush this at times. In FireFox this is done by right-clicking the site in the History window and selecting "Forget about this site". Just clearing the browser cache is not enough, in FF at least.

[rafaeldruiz]

The redirect loop is fixed, but "localhost/en" is not redirecting to "localhost/".

• "localhost/en": continued "localhost/en" and was not redirected to "localhost/" (?)
• "localhost/es": redirected to "localhost/" (ok)
• "localhost/en-US": redirected to "localhost/" (ok)
• "localhost/pt": redirected to "localhost/pt-BR" (ok)

Are you going to fix the redirect of "localhost/en"?

[turquoiseowl]

Yes, that sounds right for Scheme2.

There is a placeholder in the code called Scheme3 for /en -> / which is there for when someone wants to code it. https://github.com/turquoiseowl/i18n/issues/216

[rafaeldruiz]

Are you going to fix the redirect of "localhost/en" for Scheme2 before the submit of a new Nuget package?

[rafaeldruiz]

Any news about the fix of "localhost/en" and the new version of the nuget package?

[turquoiseowl]

The latest build is now on nuget: v2.1.5.

Scheme2 should now works as documented. The 'fix' you refer to would be Scheme3 which is awaiting implementation. I'm not sure at present when I'll have time to do that.