Note that the first request is a POST, and the second has a ? in the URL, so standard Squid configurations would treat it as non-cachable. It also looks rather “magic.
HTTP is an alternative delivery mechanism introduced with version 3 players, and it allows a reasonable approximation to “streaming” data – that is playing it as you receive it. It isn’t available in the general case: only if someone has made the realaudio file available via an HTTP server, or they’re using a version 4 server, they’ve switched it on, and you’re using a version 4 client. If someone has made the file available via their HTTP server, then it’ll be cachable. Otherwise, it won’t be (as far as we can tell.) The more common RealAudio link connects via their own pnm: method and is transferred using their proprietary protocol (via TCP or UDP) and not using HTTP. It can’t be cached nor proxied by Squid, and requires something such as the simple proxy that Progressive Networks themselves have made available, if you’re in a firewall/no direct route situation. Their product does not cache (and I don’t know of any software available that does.
Related Questions
- Note that the first request is a POST, and the second has a ? in the URL, so standard Squid configurations would treat it as non-cachable. It also looks rather ``magic.
- Is it possible to request TLC for some items but the standard service for others, perhaps by pinning a note to items needing TLC (such as dress shirts)?
- How to parameterize the parameters with the value extracted from previous URL request ?
