FMS & Apache/PHP Communication

The following is from email communication my developer had with an Adobe rep; any help to possibly circumvent this issue & specifically in answering the questions below would be greatly appreciated.  Thanks in advance!

I am using the development version to test on my server. My server is running Windows XP. I have a website that is currently running on Apache 2.2 and PHP. Without FMS, my website works perfectly.

When I install FMS, the FMS installation provides an Apache install. So I uninstalled my current Apache/PHP versions and installed only FMS. After installation, http://localhost/ takes me to the FMS page where it shows sample videos through different connections. Therefore I know the installation was successful.

After that, I install PHP and set the httpd.conf to include the PHP configuration and restart FMS. After the restart, I import my website into the webroot folder and go back to http://localhost/ so I can see my website. What shows up is my website as usual, but when I try to login, the browser says "do you want to open or save the file: process.php".

In my simple login script, PHP checks the username and password and allows the user to login if it finds a match in the MySQL database.

I remember you mentioned on the phone that even though the POST is written for PHP, that FMS tries to handle the POST and rejects it, thus giving me the error. I searched around the internet to see if anyone else has this problem, and it seems others out there do have the same problem. One such example is at http://www.flashcomguru.com/forum/forum_posts.asp?TID=4789&PN=1694&get=last but this person has not found a way to fix the problem. One suggestion on this forum was to use a standalone version of apache/PHP, but when I do that, both apache and FMS are fighting for port 80, and the one that wins is whichever was installed first. I've tried so many different ways of installing these, but none of them seem to fix the problem.

Rep reply:

I have checked and found that a bug has already been logged for this issue and is scheduled for a fix in the next major release. I wouldn’t be able to provide you timeline for the fix as these decisions are taken by the engineering team. As I had informed you earlier as the FMS is running on port 80, any request to html or php will go through FMS and hence it’s not able to process it correctly.

The engineering know about this issue and they are working on it to get it fixed by next major release. I hope that the information shared will be helpful to you.

Our last email:

Thanks for your reply; I'd like to know what my alternatives are at this point; can you please provide answers to the following:

1.  Can I utilize version 3 of the server to get arond this issue?

2.  Can I circumvent this bug by utilizing Adobe Flash Media Server on Amazon Web Services?

3.  Are both the Flash Media Enterprise Server 4 & Flash Media Interactive Server 4 affected by this bug?

4.  How have your other customers been able to circumvent this issue?

FMS and live streaming is a critical component to my website & I cannot continue to develop without it; any further guidance you may be able to provide is greatly appreciated.  Thanks again for your assistance