Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add missing assert for test "correctly redirects for a file whose fiename contains something looking like a hash" #36

Merged
merged 4 commits into from
Jan 23, 2015

Conversation

bcullman
Copy link
Contributor

The path provided in the test "/robots-3e.txt" is dehashified to "/robots.txt", which is then hashified to "/robots-ca121b5d03245bf82db00d14cee04e22.txt". This is not match for the expected url. The added assert now shows a failure.

Either we should change the expected value in the test to "/robots-ca121b5d03245bf82db00d14cee04e22.txt"
OR
We should ONLY dehashify urls that contain actual 32 character hashes

I am not certain why we would want to redirect for filenames that have something that looks like a hash, rather than actually having a hash.

Brad Ullman added 2 commits December 18, 2014 17:00
…ename contains something looking like a hash", which exposes a bug in the framework or an error in the assumption of the test.
@bcullman
Copy link
Contributor Author

only dehash when hash value is exactly 32 chars long.

@Harrison-M Harrison-M merged commit 03d7639 into mediocre:master Jan 23, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants