Hi, looks nobody reply me :(
I tried to see in source code and I found why connection is rejected.
In RTMPHandler.java#368
1.server.lookupGlobal(host,path); // host is "127.0.0.1", path is "test"
In Server.java method lookupGlobal
2.There is no "127.0.0.1/test" key in mapping property.
3.Also there is no "127.0.0.1/test" key in mapping globals.
So in the end sever.lookupGlobal returns NULL, reject connection.
I found some strange parts in server class.
1. EMPTY is "", and getKey(EMPTY, contextPath) returns "/test". But there is no
"/test" in mapping,
but "*/test" is exits.
2. Because of that the last statement of lookupGlobal
return getGlobal(mapping.get(key)); is in vain.
Because key after getKey("","") is always "/" and there is no "/" key in
globals hashMap.
So that getGlobal(mapping.get(key)) always returns null.
I don't think it is bug, but there should be in configure files to define about
global scope.
( actually I don't understand what means scope for red5.. )
And webapps/red5-default.xml is for that... But I don't know what should be
added.
Tomorrow I'm going to continue diving in this source code...
Ken Yasue
_______________________________________________
Red5 mailing list
[email protected]
http://osflash.org/mailman/listinfo/red5_osflash.org
