Hi,
I have both D6 and D7 sites with actionscript projects. Under university's internet configuration D7 site get "502 Bad Gateway" error when reaching endpoint (seen by firebug) and actionscript application give the error "NetConnection.Call.Failed". But D6 projects works normally. (At home both works normally). D7 differs by using ZEND AMF engine. I know this info is not enough (and probably I need to solve with computer center). But if you have a quick solution please provide, my D7 (http://fuzziness.org/fcm) site is related to my area. Thanks.

CommentFileSizeAuthor
#2 disable_wrong_header.patch410 bytesgarphy

Comments

rolf vreijdenberger’s picture

rolf vreijdenberger commented

Hi,
I guess the D7 project is not configured correctly with services or the server running D7 is not configured correctly. http 500 status codes are generally server related

502 Bad Gateway: The server, while acting as a gateway or proxy, received an invalid response from the upstream server it accessed in attempting to fulfill the request.
SInce it does not work there, it will not work from an actionscript application too.
I have too little information to help you any further at the moment.

garphy’s picture

garphy
Primary language French
Location Montreal, Canada
commented
StatusFileSize
new disable_wrong_header.patch410 bytes

Came across the exact same issue. When acting behind an haproxy LB, amfserver suddenly stop working.
It seems that the presence of the "powered by" http header is the cause of the panic.
"powered by" is incorrect, "powered-by" should do the trick but AFAIK this header is completely useless so we can just remove it.

Patch (probably not in correct format) provided.

aydos’s picture

aydos commented

thank you rolf and thank you garphy... you save my time :) patch works (also "powered-by" solution works). waiting for updated version.

rolf vreijdenberger’s picture

rolf vreijdenberger commented

garphy, thanks, yes, it is completely useless, guilty as charged :)
I'll remove it and update accordingly in a next release

rolf vreijdenberger’s picture

rolf vreijdenberger commented
Status: Active » Fixed

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.

babusaheb.vikas’s picture

babusaheb.vikas commented

I was getting this error too on my drupal site. i first assumed that it is server issue but it was not really a server issue. I put ini_set('memory_limit', '256M'); in index.php file and the server 502 error gone.