Using CORS Proxy for Jabber

[jmennear]

Hi,

I have access to a cors proxy server: www.corsproxy.com.

How do I make use of this so that it connects correctly?

I have a demoConfig like the following:

var jabberConfig = {

httpBindingURL: "http://10.10.10.10:7335/httpbinding",

domain: "acme.com",

username: "ausername",

unsecureAllowed: true,

password: "apassword",

serviceDiscoveryEnabled: true

Do I just add the proxy server in front of the URL like: http://www.corsproxy.com/http://10.10.10.10:7335/httpbinding?

Is there someone there that has gotten corsproxy working?

Thanks.

John

[tinghche]

Hi John,

You will need to point to the proxy entry where you have matched with the actual BOSH url.

ex from my nginx:

location /httpbinding {

            proxy_pass   http://10.10.10.10:7335/httpbinding;

}

In your example, it will be http://www.corsproxy.com/httpbinding

A quick test from your browser, just paste the proxy entry to it and see if it respond.

Regards,

Howard

[dstaudt]

I'm not sure that an external proxy like corsproxy.com is going to work, as it will try and relay the request back into your premises.  It will not be able to reach 10.10.10.10 (unless you have a port on your external IP address forwarded.)

I think you will need to setup a local/internal request proxy.  You may find the information re proxies here useful: https://developer.cisco.com/media/AJAX-XMPP-Library-Index/api/deploymentGuide.html

[basudebAcharjee231]

Hi Guys,

We did  Reverse Proxy configuration  in IIS servers where our NonGadget web Apps is deployed.

When the 1st page of our Non gadget application is displayed on the browser, it loads CISCO Jabberwerx library and other JS files. Now we call Jabberwrex functionality to start communicating with Finesse servers via our  IIS servers. In IIS server, we configured Reverse Proxy using

URL rewrite and ARR(Application Routing Request). So all requests coming from client will go through different URL rewrite rules of our IIS servers(depending on  REST API request) and then forward to the actual Finesse servers .  In this case Client will think our IIS servers is the actual Finesse servers.