Internet Explorer Error 302
Contents |
CRM 2011 Mobile Site ★★★★★★★★★★★★★★★ Austin JonesOctober 30, 20123 Share 0 0 I recently worked with a customer who had end-users encountering a strange behavior where all internet explorer 302 redirect problem attempts to access the main CRM 2011 web site were being being redirected to ie11 redirect problem the CRM mobile site (../m/default.aspx). While this is normal behavior when accessing CRM via currently unsupported browsers (Firefox, Safari, Chrome,
Internet Explorer Redirect Not Working
etc.), what made this strange was that the users experienced this behavior in Internet Explorer. The behavior was consistent for all affected users, however not all users were affected. Also, launching an In-Private
Internet Explorer 11 Redirect Not Working
browsing session in IE (ctrl+shift+P) and navigating to CRM did not produce the behavior. We decided to run a fiddler trace for an affected user where the behavior was reproduced as well as for the same user in an In-Private browser session. After capturing both scenarios we filtered down to the /default.aspx GET request and subsequent redirect/request. The reproduced scenario showed a 302 redirect response to ie 11 not redirecting properly /m/default.aspx, the CRM mobile site, and the working scenario (In-Private session) showed the expected, subsequent GET request for /main.aspx. Having successfully reproduced the behavior and captured a working, control scenario we started to compare the two GET requests for /default.aspx. What became immediately apparent was that the User-Agent header value differed between the two requests. The control scenario showed a typical profile for Internet Explorer, but most intriguing was that the reproduced scenario specified a non-IE user agent in the header. The particular element of the user agent that caught our attention was ‘Chrome/22.0.1229.94’. Why did the request appear to be coming from a Chrome browser when using IE? This discovery prompted a discussion about IE browser plug-ins and it turned out that the affected user had installed an IE plug-in from Google called Chrome Frame which is a supplementary install alongside a Chrome browser installation. This plug-in provides a Chrome-based browsing experience, for purposes of HTML5 and Chrome-optimized site support, inside of Internet Explorer. We disabled the Chrome Frame IE plug-in and the user was then able to navigate to the main CRM site successfully. This cause also explains why the In-Private session did not exhibit t
here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About
Internet Explorer Redirect Fix
Us Learn more about Stack Overflow the company Business Learn more about hiring 302 error developers or posting ads with us Stack Overflow Questions Jobs Documentation Tags Users Badges Ask Question x Dismiss Join the Stack Overflow Community Stack Overflow is a community of 4.7 million programmers, just like you, helping each other. Join them; it only takes a minute: Sign up IE doesn't follow redirect, gives “Internet https://blogs.msdn.microsoft.com/crminthefield/2012/10/30/resolved-unexplained-internet-explorer-302-redirects-to-crm-2011-mobile-site/ Explorer cannot display the webpage” up vote 6 down vote favorite I have a form with a few fields. When you submit the form, the server responds with a redirect (HTTP 302). When the form is submitted, if there is an field, IE doesn't follow the redirect, but instead gives an error: "Internet Explorer cannot display the webpage". If there is no http://stackoverflow.com/questions/6948128/ie-doesnt-follow-redirect-gives-internet-explorer-cannot-display-the-webpage field, then it does follow the redirect as expected. The HTTP 302 Response is exactly the same in both cases, differing only by the timestamp of the response. I'm experiencing this in IE8 and IE9. (I haven't tried lower versions). Firefox, Chrome, Opera and Safari all follow the redirect as expected. Notes: The form has the attribute enctype="multipart/form-data". This is happening over SSL The redirect is not to a different protocol, host, or port than the URL the form POSTs to or is hosted on. When I inspect HTTP traffic with Fiddler2, the issue disappears and IE behaves. internet-explorer http http-headers share|improve this question asked Aug 4 '11 at 20:29 nicholaides 11k94268 Odd. a 302 redirect would cause the browser to issue a GET on the target page, which would lose the uploaded file (if any). Maybe IE's error is an indication of this (and IE always has crappy error messages). Doesn't explain why Fiddler would "fix" things, though. –Marc B Aug 4 '11 at 20:32 @Marc, on the server it's a Rails app. It accepts the request, saves the file and stuff in the database, then responds with a redirect to anothe
- general The 302 response from the Web server should always include an alternative URL to which redirection should occur. If it does, a Web browser will immediately retry http://www.checkupdown.com/status/E302.html the alternative URL. So you never actually see a 302 error in a Web browser, unless perhaps you have a corrupt redirection chain e.g. URL A redirects to URL B which in turn redirects back to URL A. If your client is not a Web browser, it should behave in the same way as a Web browser i.e. immediately retry the alternative URL. If the internet explorer Web server does not return an alternative URL with the 302 response, then either the Web server sofware itself is defective or the Webmaster has not set up the URL redirection correctly. Fixing 302 errors - CheckUpDown Redirection of URLs may occur for low-level URLs (specific URLs within the Web site such as www.isp.com/products/index.html) when you reorganise the web site, but is relatively uncommon for the internet explorer redirect top-level URLs (such as www.isp.com) which most CheckUpDown users ask us to check. So this error should be fairly infrequent. The 302 response from the Web server should always include an alternative URL to which redirection should occur. If it does, CheckUpDown automatically tries the alternative URL. This in turn may possibly lead to another redirection which CheckUpDown then tries. This continues for a maximum of 5 redirections. As soon as 5 redirections have occurred, CheckUpDown gives up and reports the 302 error for your account. So you should only ever see the 302 error if 1) the Web server gives no alternative URL on the 302 response or 2) the number of redirections exceeds 5. This second condition should be fairly unlikely - and may indicate a recursive pattern e.g. URL A redirects to URL B which in turn redirects back to URL A. You first need to check that the IP name we use to check for your account is accurate. If you or your ISP have configured something so that any access using this name should now be redirected to another name, then you need to update your CheckUpDown account to sta