15

I have a website as the landing and information page to a web portal type of application.

I need the link that goes to the portal to set off an animation that beautifully transitions to the portal view (navigation slides out, new navigation slides in, various widgets fade out, new ones fade in, etc).

However, I also need the url to go from www.mydomain.com to portal.mydomain.com.

I'm willing to go to any length to have BOTH, the animation to load the portal and the url to be a subdomain.

As it stands I understand doing this would violate the security policy and not be allowed, but there is no way to achieve a fluid transition into the portal if a reload is to be had.

Is there ANYTHING that can be done? Perhaps some way to establish explicit trust between the two domains.

parliament
  • 21,544
  • 38
  • 148
  • 238
  • do you get an error from history.js when you're trying to pushState to a subdomain? – gmaliar Feb 11 '13 at 07:58
  • Indeed I am. SecurityError: The operation is insecure. – parliament Feb 11 '13 at 08:16
  • hmmm, well it seems that you can't then, because it is against the same origin policy. – gmaliar Feb 11 '13 at 09:35
  • There seems to be several ways to circumvent, http://stackoverflow.com/questions/3076414/ways-to-circumvent-the-same-origin-policy. However, I'm in need of an authoritative answer for my situation so that I don't use the wrong method and open a security vector. – parliament Feb 11 '13 at 21:45

1 Answers1

15

It can't be done. This is by design. There are no exceptions.

From the Mozilla pushState documentation:

The new URL must be of the same origin as the current URL; otherwise, pushState() will throw an exception.

Toastrackenigma
  • 7,604
  • 4
  • 45
  • 55
Sean Hogan
  • 2,902
  • 24
  • 22