Thanks for the quick answer. From the question I asked, the string provided did
include the md5 in the url without adding the extra to the file extension and
I was able to browse locally. What I was trying to accomplish was to mirror
the site and display the hash value easily for each file. I realized the local
copy does not have the same hash value as the original files on the web
server. I captured my site, I host from an IIS server and compared the md5
values with Hashtab. I believe for the method to be close to a forensic
process I should get the hash values to match. I read on a forum somewhere
that HTTrack should be able to capture the site unaltered (not it's
default)and I would assume that might accomplish the matching hash values. If
you have further input for the new information provided it would be much
appreciated. Thanks