Hi all!
I have the LS Pro Duo 1T and read this interesting thread.
I have to concur about all the problems detailed here, but I think that it lies mostly with the iPhone. (I have a V1)
MobileSafari doesn't seem to like the way the share listing is generated dynamically (by javascript only if I found right)
Besides you can't access a share (not Safari's fault since it happens also on desktop browsers) by having an address like that.
http://192.168.1.18:9000/shares/Mes_videos/ gives a 404 error. (not even listing denied)
But we can directly access a file with full path.
One solution would be that the user creates a simple "index.html" file for each folder containing files and subfolders to access.
And so I can type http://192.168.1.18:9000/shares/Mes_videos/ in MobileSafari and have a list of the folder content since I put the index file in it.
Another way would be that the NAS generates itself a virtual index.html file for each folders when we want to access a share by giving the path to it.
A .m3u file cannot be used, MobileSafari doesn't handle it.
This is an example of the index.html I put in my " Mes_videos " share.
<html>
<head>
<title>Playlist</title>
</head>
<body bgcolor="white" text="blue">
<a href="iPhone_videos/ABBA - The last video.mov">ABBA - The last video[/url]
<a href="iPhone_videos/Amy MacDonald - This is the life.m4v">Amy MacDonald - This is the life[/url]
<a href="iPhone_videos/Anna Nalick - Breathe (2 AM).m4v">Anna Nalick - Breathe (2 AM)[/url]
<a href="iPhone_videos/Delta Goodrem - In This Life.m4v">Delta Goodrem - In This Life[/url]
<a href="iPhone_videos/Stanislas & Calogero - La débâcle des sentiments.m4v">Stanislas & Calogero - La débâcle des sentiments[/url]
<a href="iBook_G4_14_Hard_Drive_Replacement.pdf">iBook_G4_14_Hard_Drive_Replacement.pdf[/url]
</body>
</html>
" iPhone_videos " is a sub folder in my share, with this I can play the files supported by my iPhone. :smileyvery-happy:
But! NOT in SSL.
In SSL MobileSafari has no problem to list the files with the index.html but it cannot play them, this is caused I think by the fact that Safari must be sending directly a multimedia link to a QuickTime layer that is incapable of handling SSL.
But, the PDF file cached (unscrambled) by Safari could be opened without problem in SSL.
A possibility would be to use a VPN connection to the NAS (without SSL of course) to have access to multimedia files.
I hope my comments helped to advance in this issue. :smileywink:
