Table Of Contents
 

Using ProFlashUpload on Clusters

Why do the uploads fail in a clustered environment?


The load balancer used in a clustered environment usually uses a cookie or URL parameter to
keep affinity with that server - i.e. the user always connects to the same server and thus keeps the same session.

Firefox Flash and Safari Flash don't automatically send all cookies along to the server when uploading the file.
Because this cookie isn't passed during the upload, the users session is lost and after the file makes it to the server, the uploadfile.cfm page doesn't recognise the current user.

How to Fix This?


You will need to view your load balancers documentation and see if we can pass a value on the URL to inform the load balancer which server to stick to.

Then you can pass in a custom attribute uploadURL, which should be the full URL path to  "dccom/components/proflashupload/uploadfile.cfm".

You then just add on the variable that will keep the user on the same server. Something like

uploadURL="http://myserver.com/dccom/components/proflashupload/uploadfile.cfm?serverId=1"

...depending how your load balancer works.