Apple Trailers/Quicktime

[darkedgex]

I'm a movie trailer lover, and normally I get trailers from Yahoo's website (even going so far as to write a smallish console app in C# which takes a Yahoo movie URL, automatically parses the linked file and creates a batch file for easy downloading). Sometimes I also download trailers from Apple's website (trailers.apple.com) and it's usually been as simple as prepending an "h" in front of a filenames size designation ("avatar2009aug0820a-tsr_1080p.mov" would become "avatar2009aug0820a-tsr_h1080p.mov" for example and that would link to the actual file which I could then remux/transcode as necessary).

But Apple seems to have recently changed their website, and now this no longer works. Looking at the linked-to MOV files I can't discern any difference in how they're handling things. The moov resources look the same. I tried changing the referer as well as looking at the incoming HTTP headers and cookies to see if maybe they were using some kind of tracking, but all instances now get 302'd back to index.html of the main site.

Anyone have any ideas for how to get around this, or what they've changed? Yes I could probably use Quicktime Pro and save them that way, but my wget method is free, and I'm a cheap bastard. :P Alternately, does anyone know of a free protocol watcher/sniffer (for Vista x64) so I can fire up Quicktime and see what's being sent/received?

Here's what wget gives me, in the event it's some obvious I'm overlooking:

D:\Trailers>wget -nd -t 0 -T 15 "http://movies.apple.com/movies/fox/avatar/avatar2009aug0820a-tsr_h1080p.mov"
--referer "http://movies.apple.com/movies/fox/avatar/avatar2009aug0820a-tsr_1080p.mov"
-U "QuickTime.7.6 (qtver=7.6;os=Windows NT 6.0Service Pack 2)"
--2009-08-20 17:52:46-- http://movies.apple.com/movies/fox/avatar/avatar2009aug0820a-tsr_h1080p.mov
Resolving movies.apple.com... 208.50.77.78, 208.50.77.62
Connecting to movies.apple.com|208.50.77.78|:80... connected.
HTTP request sent, awaiting response... 302 Moved Temporarily
Location: http://www.apple.com/trailers/ [following]
--2009-08-20 17:52:47-- http://www.apple.com/trailers/
Resolving www.apple.com... 17.112.152.32
Connecting to www.apple.com|17.112.152.32|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 24200 (24K) [text/html]
Saving to: `index.html'

100%[======================================>] 24,200 113K/s in 0.2s

2009-08-20 17:52:47 (113 KB/s) - `index.html' saved [24200/24200]

[darkedgex]

Resolved this myself, at least for Avatar (haven't tried other trailers yet). Seems their site is looking for "Host: movies.apple.com" in the headers, so fixing up wget was fairly easy:

D:\Trailers>wget -nd -t 0 -T 15 "http://movies.apple.com/movies/fox/avatar/avatar2009aug0820a-tsr_h1080p.mov"
-U "QuickTime/7.6 (qtver=7.6;os=Windows NT 6.0Service Pack 1)"
--header "Host: movies.apple.com"
I'm not sure if the user-agent is necessary, but it probably doesn't hurt. I also settled on Wireshark for my protocol analyzer. :P

Hopefully this helps anyone else wondering why downloading the full trailer locally has been impossible lately.

[kieranrk]

movies.apple.com uses akamai so the host header in fact is necessary or the server won't know what customer account to choose.

[darkedgex]

movies.apple.com uses akamai so the host header in fact is necessary or the server won't know what customer account to choose.
They must have switched to Akamai recently, heh.