Fixed the path portion of URLs that included a database identifier

According to http://fallabs.com/kyototycoon/spex.html:

>The path of the URL in the request line must be encoded by URL encoding. If the path begins with "/", the character is ignored and the trailing string is decoded. Moreover, if the path includes "/" in the middle, the segment before the middle "/" is treated as the database identifier and the next segment is decoded as the key. For example, the record whose key is "I love you" in the database "words.kch" is expressed "/words.kch/I%20love%20you" in the request line.

I have found that, instead, the keys are written to the "default" database and of the form "/words.kch/I%20love%20you" since the path portion of the URL is encode as "%2Fwords.kch%2FI%20love%20you".  In other words, the library does not allow a developer to write key/value pairs to a server that provides access to multiple databases.

The changes provided reformats the path portion of the URL to conform to the specifications described above.