Need to capture RTMP over HTTP

[Videogamer555]

I found a website that uses a rare type of streaming. Instead of the video player on the site requesting an RTMP stream using the RTMP protocol it requests it using HTTP POST messages, and the stream is returned on port 80, just like part of the website, but it is indeed RTMP protocol (not something else). Every few network packets (as analyzed with WireShark) shows that a signal is coming from the flash player in the form of an HTTP POST message, and the server is replying with a series of RTMP video packets on port 80. Is there some way to capture this? It can't be captured with RTMP capture software like rtmpdump.exe. It also can't be captured with browser plugins like Download Helper, because it depends on a video being hosted via HTTP directly (like when an MP4 video file is embedded on a web page). I need some software that can capture the RTMP video packets that come from the server in reply to the HTTP POST messages from the embedded flash player. Not sure if this will help, but the brand of embedded flash player being used on the site is Flow Player.

Looking at the exportable HTTP objects in WireShark, I have found there are 4 SWF (shockwave flash) player files that apparantly work together in the process of playing this video. So the visible interface is only one of those 4, but they are all part of the Flow Player suite of flash player files. The files are:
flowplayer.commercial-3.2.16.swf
flowplayer.rtmp-3.2.12.swf
flowplayer.bwcheck-3.2.3.swf
flowplayer.controls-3.2.15.swf

Not sure if that info will help, but it might help you guys help me to start reverse engineering the combination of protocols used in such a way that you'll be able to recommend a particular piece of software for downloading the video (assuming that there is such software that exists that's capable of intercepting this particular combination of protocols and extracting the video file itself).

Update:
The returned packets are RTMP packets it appears, but they are encapsulated in HTTP themselves, because each one has an HTTP response header, and the header specifies a MIME of application/x-fcs.