I really don't know what to call this. It seems only to happen on both Mac OSX and iOS with Safari. It doesn't seem to affect Chrome even though they are both Webkit-based.

I'm working on a B2B project where we are using Magento as the primary development framework. Linking to the site, the user must log on to do anything. I've been primarily developing on a Windows machine then pushing the code to a LEMP machine. I encounter no problems with any browser on Windows or Android.

On a Mac with Safari I link to the site. The page displays as expected. I enter my correct credentials and click on the login button. I receive a message that the server cannot be found. When I look at the address bar, I see this strangeness:


Yes, that is the URL the system wants to redirect to.

I've also seen "localhost" on iOS. I don't have localhost anywhere in the (non-database) configuration that I can find in a global search of the source code.

I did some searching looking for anything related to that broken URL and all I found were some references to turning off the SID. I did that just to see what happens, and now I receive this URL:


I've only seen this with Safari on Mac OSX or iOS.

Edit: Reloading / Relinking to the original site URL loads the site as if I were redirected there after log in.

closed as off-topic by Fabian Blechschmidt, Marius, Mufaddal, Anna Völkl, Keyul Shah Jul 25 '14 at 6:56

This question appears to be off-topic. The users who voted to close gave this specific reason:

  • "Questions describing a problem that can't be reproduced OR seemingly went away on its own (or went away when a typo was fixed) are off-topic as they are unlikely to help future readers." – Fabian Blechschmidt, Marius, Mufaddal, Anna Völkl, Keyul Shah
If this question can be reworded to fit the rules in the help center, please edit the question.


That's certainly not part of standard Magento system behavior. Unfortunately, the phrase

I'm working on a B2B project

leads me to the conclusion there's a lot of custom code in this project, which means you're unlikely to find a solution to your problem here.

Generally speaking, I'd start by adding some logging to _redirect in either your frontend of backend admin controller (depending on what "log in" means to you), and when you see a ://:... string coming though, drop a madeDebugBacktrace();exit; in there and determine which file the redirect request is coming from.

A less technical approach would be to disable all the custom extensions, and then reenable them until the behavior reemerges.

Not the answer you're looking for? Browse other questions tagged or ask your own question.