It basically allows you to allow or disallow Flash Player sockets from accessing your site.
npm install policyfile
The server is based on the regular and know
http server patterns. So it you can just listen
for all the events that a
net based server emits etc. But there is one extra event, the
event. This event is triggered when we are unable to listen on the supplied port number.
Creates a new server instance and accepts 2 optional arguments:
optionsObject Options to configure the server instance
logBoolean Enable logging to STDOUT and STDERR (defaults to true)
originsArray An Array of origins that are allowed by the server (defaults to :)
var pf = ;pf;
Start listening on the server and it takes 3 optional arguments
portNumber On which port number should we listen? (defaults to 843, which is the first port number the FlashPlayer checks)
serverServer A http server, if we are unable to accept requests or run the server we can also answer the policy requests inline over the supplied HTTP server.
callbackFunction A callback function that is called when listening to the server was successful.
var pf = ;pf;
Changing port numbers can be handy if you do not want to run your server as root and have port 843 forward to a non root port number (aka a number above 1024).
var pf =http = ;server = http;server;pf;
Support for serving inline requests over a existing HTTP connection as the FlashPlayer will first check port 843, but if it's unable to get a response there it will send a policy file request over port 80, which is usually your http server.
Adds more origins to the policy file you can add as many arguments as you like.
var pf = ;pf;pf; // now has 3 origins
Removes added origins from the policy file - you can add as many arguments as you like.
var pf = ;pf;pf; // only contains the :80 version now
Shuts down the server
var pf = ;pf;pf; // OH NVM.
MIT see LICENSE file in the repository