Skip navigation
Luis Sanchez Tapia
Currently Being Moderated

FMS proxying HTTP, problems in POP request.

Apr 16, 2012 9:45 AM

Tags: #version #fms #request #pop #developmenrt

Hello,

 

I'm using FMS development version ( last version ), I activated FMS as proxy for HTTP server, this is part of fms.ini :

 

SERVER.HTTPD_ENABLED = false

ADAPTOR.HOSTPORT = :1935,80

HTTPPROXY.HOST = localhost:82

 

On port 82 I'm running apache, that is installed from default repositories of the amazon EC2 server ( Linux AMI ), here runs a website ( Drupal ).

 

There is other website that runs in https, where we record video from webcam to FMS server and play recorded video, with no problems.

 

The problem is in http site, the navigation across the whole site works fine but not in some POST request, when I try to login into drupal admin works for all browsers in windows but not for Chrome in Linux. When I try to create a new content by web ( use a form sending info by POST ) doesn't work for any browser, looks like FMS took that request as video-stremming and doesn't pass to apache server. ( Everything on Drupal site works if we don't use FMS as proxy in port 80 )

 

What can I do to fix that? is that a bug just for FMS development version?

 

 

Thanks,

Luis.

 
Replies
  • Currently Being Moderated
    Apr 24, 2012 9:21 PM   in reply to Luis Sanchez Tapia

    Luis,

     

    I dont see any issue with either "GET" or "POST" request when I use FMS as proxy and route these requests to any other HTTP server. I tried with the same settings as you mentioned above.

    Can you let me know what FMS version are you using and also any of the request which is not being proxied I will try to simulate something similar to repro the problem.

     

    -Amit

     
    |
    Mark as:
  • Currently Being Moderated
    May 24, 2012 7:53 PM   in reply to Luis Sanchez Tapia

    We have similar problem, when FMS(port 80) is taken as proxy of Apache(port 8080).

     

    When a POST from client to server, in >50%, no response from the server, and I captured the packets using wireshark, found that no 200OK from http server.

     

    To figure out if it is the problem of Apache or FMS, we access the web form in port 8080 to Apache directly, the 200OK is sent back very immediately in 100%. So we can draw a conclusion that the problem is from FMS.

     

    So FMS guys,could you figure out how to solve it???

     
    |
    Mark as:
  • Currently Being Moderated
    May 25, 2012 11:55 AM   in reply to Luis Sanchez Tapia

    Please upgrade to 4.5.1. In 4.5.1 we made change where in Apache now is in front of FMS and proxies RTMPT traffic to FMS. So you can hit all your HTTP traffic directly to Apache without proxying it to FMS - though this would have some hit on RTMPT performance.

     
    |
    Mark as:

More Like This

  • Retrieving data ...

Bookmarked By (0)

Answers + Points = Status

  • 10 points awarded for Correct Answers
  • 5 points awarded for Helpful Answers
  • 10,000+ points
  • 1,001-10,000 points
  • 501-1,000 points
  • 5-500 points