Include the file in the URL path about gitkv HOT 1 CLOSED

I think this one we probably shouldn't do for two reasons.

If we have a file hello/world.go in a repo foo, you'll end up with a URL like this:

"/repo/foo/hello/world.go" // or,
"/repo/foo/hello/world.go?reference=sometag"

Which kind of trashes the REST approach to URLs of having the resource be a single segment of the path — and I believe quite a few web frameworks won't let you match on parts of URLs with unlimited slashes in it like this so could be boxing us into the frameworks that do allow this.

The other reason is safety: If this file path comes from anywhere dynamic, you'll need to URL escape it. If it's in the path, it isn't easy to escape everything except the slashes — whereas if it's in the query string, you can just URL escape the entire value and it'll be safe.

from gitkv.