2 ms·
We should be passing around string lists, e.g. ["foo", "bar", "baz"] instead of "foo/bar/baz". But that doesn't in and of itself solve the problem, because "fo
by wglb 12y ago
We should be passing around string lists, e.g. ["foo", "bar", "baz"] instead of "foo/bar/baz".
But that doesn't in and of itself solve the problem, because "foo/bar//baz" would map to ["foo" "bar" "" "baz"/] without any additional convention.
This is actually not that unusual. this site does not treat two consecutive slashes as a single slash. There are likely others implementation differences.
Certainly in posix consecutive slashes count as one for file paths, but URL query strings are not file paths.
- daveloyall 12y ago... "foo/bar//baz" would map to ["foo" "bar" "" "baz"/] ... No, I think it'd be more like proto://host/thing?foo&bar&baz (put an =1 on each of those if you like). Yeah, I'm employing a convention, but so to is the concept of list of strings that the commenter invoked.