121–130 of 178 posts
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.
https://foobar.withgoogle.com/staticfiles/img/sprite@2x.4d81...
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.
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…
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.
I got a little further. If you append /login to the url, you get another script: Points to: https://foobar.withgoogle.com/_ah/logout?continue=https://ww... I've tried some ways to login to appengine etc but didn't work. https://appengine.google.com/_ah/logout?continue=https://foo... I've managed to get it to log me out of my google account. Not sure what's up.
I got one like this. https://appengine.google.com/_ah/conflogin?continue=https://... Throws a 500 error.
If you are as confused as I was this old HN thread might help: https://news.ycombinator.com/item?id=8588080
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.
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…
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...