funky routing issue.  if '/a/<b>' is defined after '/', requests for '/' will route to '/a/<b>'.  i think there's a check on the lengths missing.
funky routing issue.  if '/a/<b>' is defined after '/', requests for '/' will route to '/a/<b>'.  i think there's a check on the lengths missing.

brianjpetersen/bocce