I'm working on a project which uses literal colons in URLs to specify custom methods, as per the Google API Design Guidelines. The colons do not come after a slash, as one would expect a variable to, but the engine will detect them as variables anyway because it does a simple search for single colon or asterisk characters in tree.go (in several places).
I'd like to be able to include literal colons (not necessarily asterisks, though I don't see why not) in URLs because they're valid characters, either normally when they're not immediately after a path delimiter (do we really support having paths like /root/version/something:variable?) or if they're backslash-escaped. I can make a PR to do this, but I'd like to get a sense of what's preferred (if not both).
I'm working on a project which uses literal colons in URLs to specify custom methods, as per the Google API Design Guidelines. The colons do not come after a slash, as one would expect a variable to, but the engine will detect them as variables anyway because it does a simple search for single colon or asterisk characters in tree.go (in several places).
I'd like to be able to include literal colons (not necessarily asterisks, though I don't see why not) in URLs because they're valid characters, either normally when they're not immediately after a path delimiter (do we really support having paths like
/root/version/something:variable?) or if they're backslash-escaped. I can make a PR to do this, but I'd like to get a sense of what's preferred (if not both).