Added that test case. Good catch!

I'll take too descriptive. I fixed the urls in the description to not be rendered as links anymore. Onward and upward!

I'd been considering the ranking as well. I set it to 5 kyu. When I started writing the problem it seemed "easy" but never updated the ranking as the layers of the onion were peeled off to reveal it's difficulty, so that's on me.

I've updated the description to explain more about URLs, subdomains, directories and querystrings. Can you review the new description to confirm that it's getting at the right things?

Thanks!

I think that's Ruby, Python, and Crystal approved now!

Much apologies for not having approved. I changed the description and so the merge fails. I changed it back and thought I'd approved everything (and then rolled the description forward). Give me some time and I'll approve.

Added a fix for those conditions and incorporated these into the tests. Good catch!

You prompted me to think about additional ways to break it. They're not reflected in the random tests, but I have updated the static tests to identify a number of them.

I've added some 'more random' tests as you suggested. (Good suggestion!). I think this is the sort of thing you had in mind, and it certainly makes the tests more robust. If you have another way of making better random tests I'm keen to know it.