[brserc]

I haven't been able to solve the puzzle - if there's any, however there is some interesting pattern in filenames.

/staticfiles/svg/error.33ab1eb5.svg -> 33ab1eb5 hexadecimal is 866852533, which seems to be a prime number.

I believe the probability is very low if unintended. Also other file names, can be factored more or less to 1 big prime number and few small primes.

[robryk]

These hex strings are beginnings of md5 checksums of these files:

   sh-4.3$ md5sum error.33ab1eb5.svg 
   33ab1eb5129ee5085793166d2f691dae  error.33ab1eb5.svg

I believe the point of appending them to the name is a kind of versioning: one'd want to be able to change these files and cause everyone to drop their cached version. This way when one changes a file, the filename changes too (most likely), so the cached old version will not be used.

[slig]

You're correct.

It looks like they're using Django. You can configure it to add the md5 of static files to each name. [1]

[1] https://docs.djangoproject.com/en/1.7/ref/contrib/staticfile...

[brserc]

Thanks for the explanation!

[imacomputer2]

Have you ever seen the movie PI? You sound like Max, the main character.

[axg]

The pattern is they're all hex, we need a cryptographer. The three numbers are

e6cf5ce7 67a53a45 5252068f