-
Notifications
You must be signed in to change notification settings - Fork 10.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
'flash policy port' option broken #447
Comments
But does io.configure(function () {
io.set('flash policy port', 1025);
io.set('transports', [ 'flashsocket', 'websocket', 'htmlfile', 'xhr-polling' ])
}); work? (note adding options to the listen does not work yet in the latest build) |
Curious.. the above example actually works.. The issue is when you set 'transports' before 'flash policy port'. Perhaps this is intentional but it confused me a great deal. |
Well, I think your original example also worked, you just got that debug information because by default the port is set to 843. When you include the flash socket inside the transports we will automatically start up the policyserver and start listening on the set port. On Aug 5, 2011, at 1:45 PM, tuxjay wrote:
|
No I just tested and my initial example doesn't work. If you switch the port/transport setting then the flash policy server is not restarted on a new port (confirmed with telnet). |
Thanks for checking it out, marking this issue as |
Before that commit, undefined callbacks were also added to the array, which could lead to 'Maximum call stack size exceeded' error when flush() method was called. Fixes #399
Both of these fail to set the flash policy port as per the documents and issue the standing warning about not being able to listen on 843.
The text was updated successfully, but these errors were encountered: