In article , Joe Feise
wrote:

Ron Garret wrote on 11/03/05 14:13:

In article ,
Stefan wrote:


Peter Duniho wrote:


If it's his server, then why do Quicktime files play just fine on my
computer, with a single click?

I have no idea, sometimes some combinations work and others don't, and
sometimes it's just the karma of the user. But since I have been
watching streamed QT movies from a myriad of servers with no glitch, and
since there are obviously many others who have a problem with his
server, the conclusion that the problem is at his side is valid.
Besides, if there's one installation with an absolutley clean QuickTime
environment with the newest components in the universe, then it's
certainly my Mac.


The most likely cause is that the server is sending the wrong
"Content-type" header.


Apparently not:
$ wget -S http://alexisparkinn.com/photogaller...s/747_test.mov
--00:02:02-- http://alexisparkinn.com/photogaller...s/747_test.mov
= `747_test.mov'
Resolving alexisparkinn.com... 69.36.241.130
Connecting to alexisparkinn.com|69.36.241.130|:80... connected.
HTTP request sent, awaiting response...
HTTP/1.1 200 OK
Date: Fri, 04 Nov 2005 08:02:02 GMT
Server: Apache/1.3.33 (Unix) FrontPage/5.0.2.2623 PHP/4.3.10
Last-Modified: Sun, 22 Feb 2004 00:08:50 GMT
ETag: "20cb1-b8006-4037f312"
Accept-Ranges: bytes
Content-Length: 753670
Keep-Alive: timeout=15, max=100
Connection: Keep-Alive
Content-Type: video/quicktime

-Joe

But 747_test.mov works properly in all browsers. If you're going to
check this you have to test one of the files that doesn't work:

[ron@Mini:~]$ wget -S
http://alexisparkinn.com/photogaller...0Extreme%20Lan
ding.mpg
--08:27:03--
http://alexisparkinn.com/photogaller...0Extreme%20Lan
ding.mpg
= `Boeing 747 Extreme Landing.mpg.1'
Resolving alexisparkinn.com... 69.36.241.130
Connecting to alexisparkinn.com[69.36.241.130]:80... connected.
HTTP request sent, awaiting response...
1 HTTP/1.1 200 OK
2 Date: Fri, 04 Nov 2005 16:27:03 GMT
3 Server: Apache/1.3.33 (Unix) FrontPage/5.0.2.2623 PHP/4.3.10
4 Last-Modified: Tue, 16 Sep 2003 16:14:07 GMT
5 ETag: "209ff-dea68-3f6736cf"
6 Accept-Ranges: bytes
7 Content-Length: 911976
8 Keep-Alive: timeout=15, max=100
9 Connection: Keep-Alive
10 Content-Type: video/mp4
^^^

As you can see, the file extension says it's an mpeg (which it is), but
the content-type header says it's an mp4. So any browser that believes
the content-type header will try to play it as an mp4 and barf. (This
explains why it works when you download it first, because then the
information from the content-type header is lost and the (correct) file
extension is used instead.)

rg