<br><font size=2 face="sans-serif">Hello,</font>
<br>
<br><font size=2 face="sans-serif">I don't know if I post this message
in the right place, so please excuse me if not so...</font>
<br>
<br><font size=2 face="sans-serif">I'm currently developping an embedded
HTTP server which will have to serve recorded or on-the-fly</font>
<br><font size=2 face="sans-serif">video files/streams to a VLC client
(and other clients, may be, like WMP, Quicktime, RealPlayer, etc...)</font>
<br>
<br><font size=2 face="sans-serif">All was fine with VLC 0.9.9, doing a
simple GET request served very fine by my HTTP server.</font>
<br><font size=2 face="sans-serif">Now it is not ok anymore since version
1.0.0 of VLC which I don't understand its new way</font>
<br><font size=2 face="sans-serif">of preparing a client streaming session.
I tried to compare Ethernet captures done by using Wireshark</font>
<br><font size=2 face="sans-serif">while VLC is adressing its request to
an Apache server or to my embedded HTTP server to get and</font>
<br><font size=2 face="sans-serif">display a "test.mpg" video
stream file (Apache is ok but not my own embedded HTTP server...).</font>
<br>
<br>
<br><font size=2 face="sans-serif">(1) VLC 1.0.0 <=> Apache capture
:</font>
<br>
<br><font size=2 face="sans-serif">request #1: OPTIONS / HTTP/1.1</font>
<br><font size=2 face="sans-serif">answer #1: HTTP/1.1 200
OK with additional fields, notably "Allow: GET,HEAD,POST,OPTIONS,TRACE"</font>
<br>
<br><font size=2 face="sans-serif">ok, Apache informs the VLC client that
it is supporting GET,HEAD,POST,OPTIONS and TRACE requests only</font>
<br><font size=2 face="sans-serif">(so it seems Apache not supporting PROPFIND
requests)</font>
<br>
<br><font size=2 face="sans-serif">Then, VLC 1.0.0 will continue to talk
with the Apache server without issuing any PROPFIND request...</font>
<br>
<br><font size=2 face="sans-serif">request #2: OPTIONS /test.mpg
HTTP/1.1</font>
<br><font size=2 face="sans-serif">answer #2: HTTP/1.1 200
OK (followed by additional fields about "test.mpg" file
characteristics, ok)</font>
<br>
<br><font size=2 face="sans-serif">request #3: GET /test.mpg
HTTP/1.1</font>
<br>
<br><font size=2 face="sans-serif">request #4: GET /test.mpg
HTTP/1.1 (followed by additional fields, notably further
offset in the requested file, being already partly received...)</font>
<br>
<br><font size=2 face="sans-serif">answer #3: HTTP/1.1 206
Partial Content (video/mpeg)</font>
<br>
<br><font size=2 face="sans-serif">request #5: GET /test.mpg
HTTP/1.1 (followed by additional fields, notably further
offset in the requested file, being more nad more partly received...)</font>
<br>
<br><font size=2 face="sans-serif">answer #4: HTTP/1.1 206
Partial Content (video/mpeg)</font>
<br>
<br><font size=2 face="sans-serif">and "test.mpg" file streaming/displaying
is running ok from beginning to end without any problem...</font>
<br>
<br>
<br><font size=2 face="sans-serif">Now, let's try with my own embedded
HTTP server, which seems to not work anymore, that is, not working as expected
by VLC 1.0.x !?</font>
<br>
<br><font size=2 face="sans-serif">(2) VLC 1.0.0 <=> embedded HTTP
server capture :</font>
<br>
<br><font size=2 face="sans-serif">request #1: PROPFIND /test.mpg
HTTP/1.1</font>
<br><font size=2 face="sans-serif">answer #1: HTTP/1.1 200
OK (but I don't know what additional fields I shall add ?)</font>
<br><font size=2 face="sans-serif"> .</font>
<br><font size=2 face="sans-serif"> .</font>
<br><font size=2 face="sans-serif"> .</font>
<br><font size=2 face="sans-serif">VLC tries again with more than one PROPFIND
request,</font>
<br><font size=2 face="sans-serif"> .</font>
<br><font size=2 face="sans-serif"> .</font>
<br><font size=2 face="sans-serif"> .</font>
<br><font size=2 face="sans-serif">Then VLC will finally issue GET request(s)
and the HTTP server will transfer whole "test.mpg" file blocks
to the VLC client</font>
<br><font size=2 face="sans-serif">which stays in a strange and long time-out
period (between 5 and 10 minutes ?), and then VLC is displaying</font>
<br><font size=2 face="sans-serif">the requested video stream file perfectly
!? What's the matter ???</font>
<br>
<br><font size=2 face="sans-serif">What status message shall I construct
to answer to PROPFIND requests ? It seems that VLC 1.0.x version</font>
<br><font size=2 face="sans-serif">is using some Microsoft WebDAV module
issuing at least a PROPFIND request as 1st request when talking to my</font>
<br><font size=2 face="sans-serif">own embedded HTTP server, but issuing
standard OPTIONS requests when talking to an Apache server !?</font>
<br>
<br><font size=2 face="sans-serif">What I don't understand is the difference
of 1st request to Apache ( = OPTIONS request) and to my own-developped</font>
<br><font size=2 face="sans-serif">embedded HTTP server ( = PROPFIND request,
which I don't know how to answer to exactly !? ). How VLC makes the</font>
<br><font size=2 face="sans-serif">difference, not issuing the same 1st
HTTP request when requesting the "test.mpg" file from an Apache
server or</font>
<br><font size=2 face="sans-serif">from my own embedded HTTP server ???
Can it be a "king of magic" ? I don't think so, naturally...</font>
<br>
<br><font size=2 face="sans-serif">Having no problem with VLC prior to
v1.0.x and no problem with Windows Media Player v11.xx client,</font>
<br><font size=2 face="sans-serif">so asking my customers / users to use
VLC v0.9.9 at this time, waiting/hoping me to solve the problem ASAP...</font>
<br>
<br><font size=2 face="sans-serif">1st look at WebDAV RFC is not very clear,
still don't know what exactly to add as sub-fields when</font>
<br><font size=2 face="sans-serif">constructing answer to PROPFIND request
(sub-fields like "Content-Lengh:", "Content-Type:",
"Allow:", etc...) ? </font>
<br>
<br><font size=2 face="sans-serif">Many thanks in advance for any help/suggestion
about trying to solve this unattended problem.</font>
<br><font size=2 face="sans-serif">King regards.</font>
<br>
<br><font size=2 face="sans-serif">Alain-Pierre</font>