<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic WISPr cross domain scripting feature request. in ZoneDirector</title>
    <link>https://community.ruckuswireless.com/t5/ZoneDirector/WISPr-cross-domain-scripting-feature-request/m-p/22131#M4450</link>
    <description>In trying to customize the captive portal login I came across the WISPr settings. 
&lt;BR /&gt;&lt;BR /&gt;
I want to make a captive portal that has a bit more of a granular control of how the client logs in and redirects so I started to look into writing a WISPr client in javascript for the browser. 
&lt;BR /&gt;&lt;BR /&gt;
The issue is that the client can not request outside of the origin domain unless the server gives permission. I first made a work around using img.src to load the login url into the zone director and this worked but didn't give back the response XML to the browser. Right now I am testing with the WISPr error message containing the javascript and it works well enough to play with but would be hard to manage in a large deployment. 
&lt;BR /&gt;&lt;BR /&gt;
So as a feature request, on the zoneDirector be able to have a custom Access-Control-Allow-Origin header in the WISPr service so a WISPr web client can be written in javascript for the browser using CORS.</description>
    <pubDate>Mon, 02 Dec 2013 23:18:00 GMT</pubDate>
    <dc:creator>justin_sabe</dc:creator>
    <dc:date>2013-12-02T23:18:00Z</dc:date>
    <item>
      <title>WISPr cross domain scripting feature request.</title>
      <link>https://community.ruckuswireless.com/t5/ZoneDirector/WISPr-cross-domain-scripting-feature-request/m-p/22131#M4450</link>
      <description>In trying to customize the captive portal login I came across the WISPr settings. 
&lt;BR /&gt;&lt;BR /&gt;
I want to make a captive portal that has a bit more of a granular control of how the client logs in and redirects so I started to look into writing a WISPr client in javascript for the browser. 
&lt;BR /&gt;&lt;BR /&gt;
The issue is that the client can not request outside of the origin domain unless the server gives permission. I first made a work around using img.src to load the login url into the zone director and this worked but didn't give back the response XML to the browser. Right now I am testing with the WISPr error message containing the javascript and it works well enough to play with but would be hard to manage in a large deployment. 
&lt;BR /&gt;&lt;BR /&gt;
So as a feature request, on the zoneDirector be able to have a custom Access-Control-Allow-Origin header in the WISPr service so a WISPr web client can be written in javascript for the browser using CORS.</description>
      <pubDate>Mon, 02 Dec 2013 23:18:00 GMT</pubDate>
      <guid>https://community.ruckuswireless.com/t5/ZoneDirector/WISPr-cross-domain-scripting-feature-request/m-p/22131#M4450</guid>
      <dc:creator>justin_sabe</dc:creator>
      <dc:date>2013-12-02T23:18:00Z</dc:date>
    </item>
  </channel>
</rss>

