On 5/14/10, Göran Krampe <goran at krampe.se> wrote:
> Hi!
>
> So, one way to "screw it up" is to register a release with a URL that
> fails - say returns a 404. SM will then consider that result to be the
> correct result and compute an SHA hash and store the 404.html file as
> the cached "proper file". When the real file is placed on that URL it
> will not work since the SHA hash will be different and SM will instead
> rely on the cached file (which of course is a silly 404.html).

This is the description of a bug. If an URL returns 404 and SqueakMap
still has a file cached it should not overwrite the cache version with
404.html

--Hannes