ejabberd - Comments for "flash-policy-file - Serve cross domain policy file for Flash"

unable to access crossdomain.xml

rafay — Wed, 27 Jul 2011 11:03:53 +0000

Hi
I am using ejabberd 2.18 version and installed it on Windows (x64bit) server.

I am developing a web client for chat and accessing the ejabberd server on port no: 5280

The issue I am facing is with the crossdomain policy.

I have gone through various posts in this forum as well as on other resources. Tried out the possible solutions , but every thing
has failed to address the issue.

I need a detailed explanation of how to host crossdomain.xml on port no. 5280.

Thanks

Thanks, Badlop. I tried it in

GP — Sun, 14 Feb 2010 16:13:54 +0000

Thanks, Badlop.
I tried it in ejabberd-2.1.2 it works like charm, also have updated the same in ticket column

Patch updated

mfoss — Tue, 02 Feb 2010 22:07:36 +0000

Quote:

would looking for support of this patch on the latest version of ejabberd 2.1.2 or 3.0 and also would be nice if it be part of the ejabberd main source base

I've updated the patch to apply in ejabberd 2.1.2/2.1.x. See the ticket EJAB-960.

would looking for support of

GP — Mon, 01 Feb 2010 16:42:10 +0000

would looking for support of this patch on the latest version of ejabberd 2.1.2 or 3.0 and also would be nice if it be part of the ejabberd main source base

Not working

crash2burn — Tue, 23 Jun 2009 14:03:19 +0000

New patch @ https://support.process-one.net/browse/EJAB-960

But it does not work for me - attempting to get it fixed, vote up the ticket if you are having issues as well.

Ubuntu package with patch applied

lazzarello — Tue, 20 Jan 2009 23:15:00 +0000

At Launchpad.

Serve cross domain policy file for Flash - patch "4"

MikeDunne — Thu, 03 Jul 2008 23:51:33 +0000

The strengths of this patch are the result of a number of iterations modifying the code to:

1. only fire on exception
i.e. policy file request format generates xmlns error, so, test for policy file request and response logic put in xmlns error handling routine.
2. automatically reports ports on which ejabberd c2s is listening for xmpp. Generally, this will be 5222, however, some servers might want to use other, non-standard ports.
Ports are not hard-coded in patch. ejabberd.cfg defines listen ports, the patched code identifies the active listen ports. Nice trick by badlop.

If anyone wants script (bash or bat) to use for testing patch without using flash, let me know.