Http Error 302 Internet Explorer
Contents |
CRM 2011 Mobile Site ★★★★★★★★★★★★★★★ Austin JonesOctober 30, 20123 0 0 0 I recently worked with a customer who had end-users encountering a strange behavior where all attempts internet explorer 302 redirect problem to access the main CRM 2011 web site were being being redirected to the
Http/1.1 302 Found
CRM mobile site (../m/default.aspx). While this is normal behavior when accessing CRM via currently unsupported browsers (Firefox, Safari, Chrome, etc.), ie11 redirect problem 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 browsing session
Internet Explorer Redirect Not Working
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 /m/default.aspx, the CRM ie not redirecting to https 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 the behavior since browser plug-ins are disable
- 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 the alternative
Http 303
URL. So you never actually see a 302 error in a Web browser, unless
Fiddler
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 Web server does not return https://blogs.msdn.microsoft.com/crminthefield/2012/10/30/resolved-unexplained-internet-explorer-302-redirects-to-crm-2011-mobile-site/ 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 top-level URLs (such as www.isp.com) which most CheckUpDown http://www.checkupdown.com/status/E302.html 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 start using the new name. If you believe that the IP name we use is exact (shoul
Case and Cooling Fetish CPU & Motherboard Technologia Mobile Computing Outpost Networking Matrix Other Hardware Agora Classifieds Ars DIY Forum (Name TBD!) Operating Systems & Software Battlefront Microsoft OS & Software Colloquium Linux Kung Fu http://arstechnica.com/civis/viewtopic.php?t=1159718 Windows Technical Mojo Distributed Computing Arcana Macintoshian Achaia Programmer's Symposium The Server Room Ars Lykaion Gaming, Extra Strength Caplets The Lounge The Soap Box The Boardroom The Observatory https://answers.yahoo.com/question/?qid=20090613115155AAPlWS9 Ars Help & Feedback Ars Subscription Member Areas Image Galleries PHP: 302 redirects work in every browser but IE 18 posts GohanIYIan Ars Praefectus et Subscriptor Registered: Oct 17, 2002Posts: 4666 Posted: Mon Oct 31, 2011 12:59 pm For internet explorer $deity's sake it's not even a rendering issue, it's HTTP protocol. This is what I'm doing:Code:if (!isset($_SERVER['HTTPS'])){ header("Location: https://complete.url/page"); header("Connection: close"); die();}I suspect it has something to do with the fact that I'm redirecting to the same host, but I'm at a loss what the actual issue is. If I redirect from an http page to another http page, there's no issue.According to fiddler, IE (8, XP) is receiving a proper-looking http error 302 302 response, but then it does nothing. No new request is issued. A DNS problem seems unlikely since the host doesn't change. If I browse the https URL directly in IE I don't get any certificate errors or warnings. I've tried using a 301 instead and that makes no difference.Is there any good way to coax real debug info out of IE beyond the "Cannot display page" page? kedlav Ars Centurion Registered: Feb 10, 2011Posts: 213 Posted: Mon Oct 31, 2011 4:44 pm Not that I really know of, but I'll ask the more general question of why are you using code based redirects instead of using webserver configuration? Hardcoding redirects is typically considered a very bad practice. Xon Ars Scholae Palatinae Registered: Nov 24, 2004Posts: 978 Posted: Mon Oct 31, 2011 10:00 pm "Connection: close" is a http/1.1 bit if it's being sent over a http/1.0 connection all bets are off. technophile Ars Legatus Legionis Tribus: Ogden, UT Registered: Aug 3, 1999Posts: 20964 Posted: Mon Oct 31, 2011 11:21 pm Also check that nothing is being sent to the browser prior to that header; that's a common PHP issue IME. koala Ars Praefectus Tribus: Barcelona, Spain Registered: Dec 31, 2001Posts: 4433 Posted: Tue Nov 01, 2011 5:57 am Yeah, I hadn't seen the close connection bit, I've never used that so you might want to try removing it- I'm not sure that belongs to the
Help Suggestions Send Feedback Answers Home All Categories Arts & Humanities Beauty & Style Business & Finance Cars & Transportation Computers & Internet Consumer Electronics Dining Out Education & Reference Entertainment & Music Environment Family & Relationships Food & Drink Games & Recreation Health Home & Garden Local Businesses News & Events Pets Politics & Government Pregnancy & Parenting Science & Mathematics Social Science Society & Culture Sports Travel Yahoo Products International Argentina Australia Brazil Canada France Germany India Indonesia Italy Malaysia Mexico New Zealand Philippines Quebec Singapore Taiwan Hong Kong Spain Thailand UK & Ireland Vietnam Espanol About About Answers Community Guidelines Leaderboard Knowledge Partners Points & Levels Blog Safety Tips Computers & Internet Programming & Design Next How do I fix a 302 error on my website? I looked at the AwStats for my website and it shows a few people getting 302 errors. What causes these errors and how do I fix it? How can I find out what the problem is? 1 following Report Abuse Are you sure you want to delete this answer? Yes No Sorry, something has gone wrong. Trending Now Natasha Stoynoff Miranda Lambert Che Guevara Minnesota Vikings Car Insurance Mortgage Calculator Odell Beckham Arthritis Relief Annette Bening Anthony Foley Answers Relevance Rating Newest Oldest Best Answer: 302 is not an error. It is the HTTP status code for "moved temporarily," which tells the Web browser / search engine that it should continue using the URL it used in the first place. A 302 redirect is common when using mod_rewrite, PHP's header() and other such URL-changing schemes. People will tell you 302 redirects hurt your search engine rankings. That's bunk; there's so many of them out there, they're largely ignored. However, you can change redirection methods to send 301 -- moved permanently -- instead, if you are especially paranoid. AWstats puts all response codes that aren't 200, including those that resulted in succe