Home javascript android java php c# ubuntu python c++ c ios TAGS

Cross domain local storage library stops working upon deploying via IIS


Date : 2019-05-02 13:37:41 , By : Gargaroz

I have two different AngularJS web-apps deployed locally using wildfly + IIS (www.sitea.ab.company.com) and just wildfly (www.sitea.ab.company.com:8080).

The first one is always executed first and stores data inside localStorage, while the second one is always opened later using the aforementioned data within the localStorage.

I'm trying to access the first web-app localStorage from the second web-app via this cross-domain-local-storage library, and everything works just as expected while developing and using respectively localhost:9000 and localhost:3010.

Alas, as soon as both web-apps get deployed the cross domain local storage mechanism stops working, more in particular:

  • the 2nd web-app script finds the needed 1st web-app index page
  • the 2nd web-app script asks for specific data (defined and with a proper value) stored in the 1st web-app localStorage
  • BUT the 2nd web-app gets always value: null for that key

I encountered this problem using both Chrome and IE11, and so far I tried this solution by adding X-Frame-Options ALLOW-FROM sitea.ab.company.com:8080 via IIS Configuration Editor of sitea.ab.company.com but nothing changes (even though I restarted both IIS and the browser with a fresh new cache).

Can you help me find what is going wrong and fix it, basing on these pieces of information?

TAGS : dns
- Technology - Yellow pages
» java
» php
» c#
» ubuntu
» python
» c++
» c
» ios
» jquery
» html
» sql
» r
» mysql
» linux
» access
» iphone
» css
» excel
» vb.net
» .net
» ruby
Privacy Policy - Copyrights Notice - Terms - Contact Us 2019 © tinytut
Licensed under cc by-sa 3.0 with attribution required.