> Sorry about the delay.
NP ;-)
> Here are the two links. The later resides on a Windows
Media Server.
Well I dunno how Windows Media Server is supposed to work,
but I tried
this:
<cfhttp URL="
http://65.61.124.134/nonsense_file.dat"
method="get"
result="stFile3">
And it returned an HTTP status of 200. Odd.
You should perhaps read the docs on Windows Media Server adn
see if there's
an explanation as to why it returns "200" for every request.
And maybe
they'll also explain how to glean if the file actually DIDN'T
exist.
Bottom line: this is not a problem with CF, it's a problem
with how WMS is
responding to HTTP requests, or the way we'd EXPECT WMS to
respond (ie:
with a 404 if the file doesn't actually exist).
--
Adam