[vlc-devel] rtsp-http-port disabled in web plugin

[Guy Perkins]

Hi, sorry to butt in, but would it not also make sense to have an
alternate port if the page was to be hosted "within" a company's own
network for internal use, & thus they may want their internal clients to
automatically resolve to a port other than 80 for security, so they
could differentiate it from (port 80 going out traffic) so to speak?
-----Original Message-----
From: vlc-devel-bounces at videolan.org
[mailto:vlc-devel-bounces at videolan.org] On Behalf Of John Smith
Sent: 16 May 2011 21:16
To: Mailing list for VLC media player developers
Subject: Re: [vlc-devel] rtsp-http-port disabled in web plugin



It does make sense (in my case at least) because vlc is preventing me
from connecting to a server on a different port (8080) which is the port
they use (apache is on port 80).




2011/5/16 Rémi Denis-Courmont <remi at remlab.net>


Le lundi 16 mai 2011 21:47:57 John Smith, vous avez écrit :

> I noticed that rtsp-http-port has been disabled in the webplugin,
meaning
> that only the default port (80) can be used when streaming rtsp over
http.
>
> What was the reason for this? Security or something else?


It makes no sense for the server/webpage to control the RTP source
client
port, and thus rtp-port is not allowed (it's kinda as if a webpage would
configure the HTTP proxy!). For rtsp-http-port, I don't know.

--
Rémi Denis-Courmont
http://www.remlab.info/
http://fi.linkedin.com/in/remidenis
_______________________________________________
vlc-devel mailing list
To unsubscribe or modify your subscription options:
http://mailman.videolan.org/listinfo/vlc-devel



-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.videolan.org/pipermail/vlc-devel/attachments/20110516/c2bff0a9/attachment.html>