<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
Thank Ross for your rapid answer<br>
<div class="moz-signature"><font color="#000000"><br>
Basically, I want to have in the same computer a web server (in
my example apache) and the live555 media server as RTSP server,</font><font
color="#000000"> therefore I need apache working as an HTTP
proxy for RTSP requests (?)... but in my tests it did not work.
(I don't know if I need to setup anything more in any of the
system parts)<br>
<br>
My last statement was about if another possibility to do that </font><font
color="#000000">exists, that is,</font><font color="#000000">for
example: live555 has its own HTTP server that is able to receive
HTTP requests for serving webs as well as RTSP requests and then
avoid using apache.<br>
<br>
<br>
<br>
</font></div>
<br>
On 12/21/2011 01:21 PM, Ross Finlayson wrote:
<blockquote
cite="mid:CC75570B-29E1-4F04-8585-1DF030ED012F@live555.com"
type="cite">In general, I see no reason why RTSP-over-HTTP would
not work through a HTTP proxy.
<div><br>
</div>
<div>However, I'm confused by your last statement:<br>
<div>
<blockquote type="cite">
<div bgcolor="#ffffff" text="#000000">Is there any other
possibility in order to support RTSP over HTTP and a web
service over 80 port in the same machine?<br>
</div>
</blockquote>
</div>
<br>
</div>
<div>By this, do you mean a RTSP-over-HTTP client (e.g.,
"openRTSP"), or a RTSP server (such as ours) that supports
RTSP-over-HTTP?</div>
<div><br>
</div>
<div>Obviously, a RTSP server cannot use port 80 for
RTSP-over-HTTP if there is already a HTTP server on the same
machine that also uses port 80. No 'proxying' can make that
possible.</div>
<div><br>
</div>
<div>Note, though, that our server code (as illustrated by the
"live555MediaServer" and "testOnDemandRTSPServer" applications)
will not use a port number for RTSP-over-HTTP (or for just plain
RTSP) if there is already another server on the same machine
using that port.</div>
<div><br>
</div>
<div><br>
</div>
<div>However, there's no reason why a RTSP-over-HTTP client (such
as "openRTSP") can't access a *remote* RTSP server over port 80,
even if there is already a HTTP server running on the client's
machine. (Just as long as there isn't a HTTP server (using port
80) already running on the *remote* machine.) You should not
need a proxy to do this.</div>
<br>
<br>
<div apple-content-edited="true">
<span class="Apple-style-span" style="border-collapse: separate;
color: rgb(0, 0, 0); font-family: Helvetica; font-style:
normal; font-variant: normal; font-weight: normal;
letter-spacing: normal; line-height: normal; orphans: 2;
text-indent: 0px; text-transform: none; white-space: normal;
widows: 2; word-spacing: 0px; font-size: medium;"><span
class="Apple-style-span" style="border-collapse: separate;
color: rgb(0, 0, 0); font-family: Helvetica; font-style:
normal; font-variant: normal; font-weight: normal;
letter-spacing: normal; line-height: normal; orphans: 2;
text-indent: 0px; text-transform: none; white-space: normal;
widows: 2; word-spacing: 0px; font-size: medium;">Ross
Finlayson<br>
Live Networks, Inc.<br>
<a moz-do-not-send="true" href="http://www.live555.com/">http://www.live555.com/</a></span></span>
</div>
<br>
<pre wrap="">
<fieldset class="mimeAttachmentHeader"></fieldset>
_______________________________________________
live-devel mailing list
<a class="moz-txt-link-abbreviated" href="mailto:live-devel@lists.live555.com">live-devel@lists.live555.com</a>
<a class="moz-txt-link-freetext" href="http://lists.live555.com/mailman/listinfo/live-devel">http://lists.live555.com/mailman/listinfo/live-devel</a>
</pre>
</blockquote>
</body>
</html>