Skip to main content
H
honggang_li
Known Participant
May 25, 2012
Question

FMS httpproxy problem, no response to POST form, no 200OK

  • May 25, 2012
  • 2 replies
  • 1988 views

We have an urgent 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???

This topic has been closed for replies.

2 replies

H
honggang_liAuthor
Known Participant
May 25, 2012

We have locked the potential reason behind, the interaction between AJAX engine on browser and FMS server(httpproxy), the facts we found are:

- non-AJAX transaction can be processed properly, from whichever IE or Chome

- AJAX transaction, the one from Chrome can work well with FMS http proxy

- AJAX transaction, the one from IE cannot work well with FMS http proxy, with long long latency, several minutes maybe

- AJAX transaction, the one from IE cannot work well with Apache directly

FMS guys, please act!

S
Adobe Employee
SE_0208
Adobe Employee
May 25, 2012

Which FMS version are you using? In 4.5.1  - we made one change - where now Apache listens on 80 and it proxies RTMPT traffic to FMS. Can you try that if that solves your problem. Is it possible for you to uprgade to 4.5 if you are on 4.0 or its not possible?

H
honggang_liAuthor
Known Participant
May 26, 2012

What we use is 4.5.

One question, is the Apache you mentioned an independent one or the one binded with FMS?

We will try 4.5.1, please give us more details on how to make Apache proxies RTMPT traffic?

Thanks

H
honggang_liAuthor
Known Participant
May 25, 2012

Interestingly, we test it using IE browser and Google Chrome(or Firefox), with Chrome, the problem disappeared, the problem only exists with IE? it is weired, we guess it may be related to AJAX operations.

With httpproxy, AJAX works abnormally, am I right?

Terms & ConditionsAccessibility statement
Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices