I confirm that suggestion works. Respectfully and without meaning to nag: please do continue to consider the patch for future inclusion. I note this isn't the first time I've encountered issues with LIVE555 streaming media and trailing slashes. If I recall correctly, it wasn't possible for a client based on LIVE555 SM to send repeated describe commands - sequentially and periodically, to acquire updated stream duration for a live stream - to a server also based on LIVE555 SM because of a spurious trailing slash. We worked around that issue by sub-classing RTSPClient to expose setBaseURL(), and then calling setBaseUrl() before sending each describe command to reset/correct the base URL. Again, respectfully: these sorts of niggly issues can get a bit annoying!
Thank you once again for your support. P.S. In a previous interaction (http://lists.live555.com/pipermail/live-devel/2015-August/019584.html) you asked me to let you know when we'd managed to update to the latest version of LIVE555. I finally managed to get that ball over the hill! Our project: http://www.team-mediaportal.com _______________________________________________ live-devel mailing list live-devel@lists.live555.com http://lists.live555.com/mailman/listinfo/live-devel
