Did you have to do something special to make this happen for you? Our standard Red 5 install just rolls to rtmpt (port 80/http) whenever a connection with rtmp (port 1935) fails - just like FlashComm does.
muriel bowie wrote: > dear list, > > we have implemented an automated fallback method to switch from rtmp > to rtmpt when the connection fails. we have successfully tested it on > one of our routers with port 1935 blocked, but we have recently > discovered that the fallback does not work for all routers. the only > difference we could discover between the routers is that one issues > HTTP 1.0 requests and the other HTTP 1.1. When HTTP 1.0 is issued, > Red5 either says "Close, not connected" or doesn't react at all. With > HTTP 1.1 everything works fine. Is this related with HTTP 1.1's > persistancy handling? And is there a workaround for this without using > Apache? > > thanks, > muriel > ------------------------------------------------------------------------ > > _______________________________________________ > Red5 mailing list > [email protected] > http://osflash.org/mailman/listinfo/red5_osflash.org > _______________________________________________ Red5 mailing list [email protected] http://osflash.org/mailman/listinfo/red5_osflash.org
