Web plugin: rtsp-http-port option ignored

[Nanocity]

Hi all,

Web plugin is ignoring rtsp-http-port option, as far as I know, because it is not marked as "safe" in live555 demux.
I have seen several post (1) requesting to make this option available for the plugin but no changes has been made on this.
I would like to know why is this option unsafe and should not be set by the plugin or if this is an issue/bug and it will be add as an option in future releases.

I need it because I have other services running on port 80 and trying to proxy the request with Apache, Nginx or Lighttpd won't work because of the oversized Content-Length of the POST request.

Thanks for the great job and sorry for my english.

(1)
viewtopic.php?f=16&t=72349
viewtopic.php?f=16&t=65712
http://mailman.videolan.org/pipermail/v ... 80025.html

[RSATom]

I can add "rtsp-http-port" to fbvlc (https://code.google.com/p/fbvlc/) if it will be usefull.

[lestoilfante]

I need this feature too!!
Please let us know about future implementation or if it is a bug

[mstavrev]

I need the option too. Any progress?

[RSATom]

You didn't answer, are you ready to use fbvlc or you need this option only in original web plugins?

[mstavrev]

Hello,

The original plugin, installed via VLC Media player setup registers an ActiveX for IE usage and NPAPI plugin that is usable by FF and Google Chrome.
In case fbvlc can provide the same functionality under those three major browsers I don't see a reason not to use it.

So, basically I need to understand:
- Will it work under Google Chrome (the original VLC plugn does work)?
- Will it work under IE, e.g. is the fbvlc register an ActiveX control? If so, what's the classid, or it is no longer needed?

Thank you

[RSATom]

1) fbvlc works on firefox|chrome|opera|ie on windows (maybe except of 64 bit versions).
2) fbvlc does not register mime types, so it plays only media directly pushed to it. It's the main difference from original web plugins, which replace other registered mime type handlers.
3) all browsers accept fbvlc by the same code:

Code: Select all

<object type="application/x-fb-vlc" width="320" height="240"> </object>

4) yes, fbvlc registers activex, but it's anyway used by above code.

[mstavrev]

Thank you for the prompt response.
After the above notes I think fbvlc is completely usable.

Can you please, add the support for the rtsp-http-port option? I've tested the latest version published on SourceForge - FBVLC_0.0.6_VLC_2.0.8, but it seems to still ignore it.

Thank you

[RSATom]

Yes, I didn't add it yet. But ok, will add to the next version.

[mstavrev]

Thank you. Please drop a post here when there is such version available.
Btw, do you know why the orginal VLC control prevents this option from being used? Is it filtered out due oversight, a bug or just some security policy?

[RSATom]

Thank you. Please drop a post here when there is such version available.

Ok

Btw, do you know why the orginal VLC control prevents this option from being used? Is it filtered out due oversight, a bug or just some security policy?

Don't know, but I think just original developer initially marked it as unsafe, and since that time nobody care... Maybe it's really unsafe, I don't sure.

[mstavrev]

Yes, I didn't add it yet. But ok, will add to the next version.

No pressure, but is there a rough estimation when this enhancement shall be available? May be a pre-release I can test?

[RSATom]

I think it will be today or tomorrow. Anyway, if you can, you could build fbvlc by yourself - patch already in repo ( http://code.google.com/p/fbvlc/source/d ... 9abcd5bd8c )

[RSATom]

uploaded. https://sourceforge.net/projects/fbvlc/ ... C%200.0.7/

[mstavrev]

Thank you, I confirm the rtsp-http-port option now works flawlessly.

[RSATom]

thanks, since I can't test it by myself.