Safari can't open the page Too many redirects occurred trying to open "https://developer.apple.com/contact/submit.php".

I get the following message when trying to open the developer.apple.com/contact/submit.php site:


Safari can't open the page

Too many redirects occurred trying to open "https://developer.apple.com/contact/submit.php". This might occur if you open a page that is redirected to open another page which then is redirected to open the original page.


I need to contact Apple because something is wrong with my Developer enrollment which I have already been charged for (so I am not happy).


This is not a good way to start. :-/

iMac, OS X Mountain Lion (10.8.3)

Posted on Apr 15, 2013 10:49 PM

Reply
16 replies

Apr 15, 2013 11:41 PM in response to Trent101

I tried to access the same site in Google Chrome which provided the following information (looks like it might be an issue with the website)


This webpage has a redirect loop

The webpage at https://developer.apple.com/register/completeRegistration.action?cancelURL=https %3A%2F%2Fdeveloper.apple.com%2Fprograms&successURL=https%3A%2F%2Fdeveloper.apple .com%2Fcontact%2Fsubmit.php has resulted in too many redirects. Clearing your cookies for this site or allowing third-party cookies may fix the problem. If not, it is possibly a server configuration issue and not a problem with your computer.

Here are some suggestions:

Error 310 (net::ERR_TOO_MANY_REDIRECTS): There were too many redirects.

Apr 16, 2013 10:18 PM in response to Trent101

The official word from Apple is here:


http://support.apple.com/kb/TS3320



Symptoms

When trying to view a website using Safari, you may see the alert message: "Could not open the page. Too many redirects occurred trying to open (website name)." This may occur if you open a page that is redirected to open another page, which is then redirected to open the original page.

Resolution

This issue is typically caused by the website you're trying to view, not by Safari. Safari may be able to open the website at a later time, when the website's redirect problem has been corrected.
Occasionally, the issue might be caused by an interaction with Safari. The issue may also occur because redirect information has been retained beyond its useful life. In some cases, resetting Safari may allow you to regain access to a website. To do that, follow these steps:

  1. Choose Safari > Reset Safari.
  2. Only check "Remove all cookies" and "Empty the Cache."
  3. Click Reset.

If the issue persists, sending feedback to the affected website may help. You can also send feedback to Apple by choosing Safari > Report Bugs to Apple.

Apr 16, 2013 9:17 PM in response to Trent101

Fortunately, Apple released the hold on my account for the Developer Program and I have successfully activated it. The redirect problem is still an issue though that I hope Apple will fix soon as it appears to be a problem on that particular webpage. I read that there is a specific bit of code that checks for the kind of browser and device which might be getting in a loop. I will try to locate the where I found the information and post back here.

Apr 16, 2013 10:24 PM in response to Trent101

This was a helpful explanation I found regarding why the error might be happening:


http://macmost.com/forum-can-you-explain-a-bit-about-safaris-too-many-redirects- error.html



Gary Rosenzweig says: 1/10/12 at 3:01 pmWell, the basic error means exactly what it says. For those that don’t know, a redirect is when a web site automatically takes you away from the page you were on to another page. For example, you may go to example.com. But that page will automatically redirect users based on, say, their location. So US users go to example.com/usa.html and Canadian users go to example.com/canada.html. That’s a redirect.
Another reason may be due to the browser type. So one page for desktop users, another for mobile, etc.
But web site may have a problem where it endlessly redirects someone. For instance, if you are in Brazil then the redirect may go to brazil.html. But the developer forgot to make a brazil.html, so it redirects to the home page, which then goes to brazil.html again, etc. Browsers can detect this and stop the endless loop, giving you instead a “too many redirects error.”
So why might this be happening? It depends on the web site and the specific situation. Cookies can enter into it as they are another piece of information like location or browser type. For instance, you go to a site and enter your zip code. That is saved in a cookie. Later, when you return to the web site it identifies that cookie and automatically tries to take you to a page using that zip code information. But an error occurs and it ends up going back to the original page and the loop begins. In that case, clearing that cookie solves the problem for the user, at least temporarily.


Apr 17, 2013 6:53 AM in response to Trent101

My problem persist, I clear cache, cookies, temp files, etc... don't working.

I try use IE, Chrome ans Safari and the error is the same.


@Trent101 I have a problem with my "Developer enrollment" too and I don't receive the email to activate it.

How you resolve this? Because without this site working I can't sent email to support or there is another way?


Thank you

Jun 30, 2014 9:21 AM in response to Rlvn22

Exactly!! As with any other server based systems that rely on syncing of information, Dates and Times MUST be within a period of time (usually 30 seconds) of the server and client to work correctly. If they are off more than 30 seconds between the two, they will not sync, or connect in this case.


I just fixed this problem on a 15" MBP with Retina for a friend of mine who was experiencing this problem.


Set the date/time to sync automatically off of a public time-server, and all's right with the world.


So, just to be clear... MAKE SURE THE DATE AND TIME ARE CORRECT AND THIS ISSUE *SHOULD* BE RESOLVED.

Sep 15, 2014 7:34 PM in response to Trent101

Okay, I had to sign up for this board just to point my finger and shout out a hearty Nelson HA-HA.


Apple is incapable of admitting when it ships defects in its products, yet here we have a scenario in which one product not being broken is mutually exclusive to the other not being broken. This is the Apple equivalent of dividing by zero.


That Safari gives up when it encounters two HTTP 3XX redirects in a row is ridiculous. That it caches the /quit so hard that it requires a full browser reset before trying again is stupidity on an order of magnitude far beyond that of mere mortal programmers. I mean, I understand the sentiment. There's no excuse for sloppy redirects. But no other web browser has ever handled this so clumsily. Apple needs to get their act together and do something about this. It's embarrassing.

This thread has been closed by the system or the community team. You may vote for any posts you find helpful, or search the Community for additional answers.

Safari can't open the page Too many redirects occurred trying to open "https://developer.apple.com/contact/submit.php".

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple Account.