You will recieve your password to this address. Address is not made public.

Your preferred username that is used when logging in.

Flow Player Control Failing in 2 ways Created Aug 9, 2010

This thread is solved

Views: 1367     Replies: 1     Last reply Aug 9, 2010  
You must login first before you can use this feature

Jamie Fox
Jamie Fox: Web guy for a more than a decade. http://www.jamiefox.net

Posts: 1

Registered:
Aug 9, 2010

Flow Player Control Failing in 2 ways

Posted: Aug 9, 2010

We have created a scroller control using JavaScript to move between videos in the Flow Player. However, in the production load balanced environment that scroller does not render. This is in a Microsoft web server using Cisco load balancing hardware. We are seeing two problems.

1) The scroller does not render in the load balanced environment. If an alternate host name is created so that requests could be directed to a particular PROD server instead of going through the load balancer the video scroller section display works.
2) The scroller does not render when anonymous authentication is turned off in IIS.

Any help would be appreciated.

Jamie Fox
http://www.jamiefox.net

Buzz
Author of 'Wordpress Flowplayer', jQuery.saiweb http://saiweb.co.uk Problems, requests? Please log a ticket at: http://trac.saiweb.co.uk

Posts: 271

Registered:
Dec 17, 2008

» Flow Player Control Failing in 2 ways

Posted: Aug 9, 2010

Reply to: Flow Player Control Failing in 2 ways, from jamiefoxva
Hi Jamie,

1) Check the media is being replicated correctly, the controls are loaded separately to the player, this error indicates a server is not returning the controls.swf, check using firebug for a 404/403

2) Sorry ditched windows years ago, IIS is no longer my "thing"

Somewhere else to check is the session persistence on you Cisco, and if you managing this hardware dump out the requests made and served, your ISP can also do this, _IF_ everything is returning 200 OK please provide the following (if you can)

a) Test page
b) IP of LB
c) IP of each webserver
i) Each webserver must be accessible on port 80 and respond to this ip.

I work with numerous linux and layer3/7 loadbalancing technologies and have a tirade of scripts I use for diagnosing these problems.

Cheers

Buzz