We solved problems...but we don't know what was the exact cause of problem.
first...if we use URL like webseal_ip/.../publish_point
, WMS returns a.wvx like meta file. (if the player doesnot support wvx file extenstion, it creates popup windows(download or execute))
As you mentioned, webseal rewrites the streaming media URL.
but there was one strange thing.
WMS gives Webseal that http response as http version 1.0, but Webseal gives player that response as http version 1.1.
I think the player cannot understand that respose and retry...
second..we use URL like mms://webseal_ip/jct/publish_point
it works well through http protocol.
(webseal cannot handle mms or rtsp protocol, so client failed
connect by that protocol and finally success http protocol.
the difference first and second is...
In fisrt method...the user-agent(http spec) was NSPLAYER WMFSDK (i think this is IE media player plug-in)
and returns wvx meta info and use http 1.0
the second method, the user-agent was just NSPLAY with
auth infomation and dose not return wvx and use http 1.1
I suspect the problem was....webseal changed backend webserver's response from version1.0 to version1.1
and using http:// invoke IE plug-in
thanks a lot
Oct 21 2007 by
RYU GUN WOO