mleku @mleku - 1d
don't just submit to the stupidity of arbitrary nonsense recommend... in RFCs they use the SHOULD verb a lot for this case, meaning this is preferred because it maes implementation more clear and differences in implementation should be avoided if possible, because they lead to remapping errors, so define a standard mapping, and you will have no problems with people who want to use apache vs nginx or their own homespun golang or C http server
the git-http protocol is simply a http file protocol, it uses paths, natively
it's just a variant of what is done with SSH the reason why i'm needling about the remapping is because i know this, and i know how http lets you remap to whatever, but leaving out stipulations in specifications leads to interop problems and you simply don't want that, idk how this is hard for you to understand implicit things are fine in idiom so long as you can easily find them explicated too often, they are not, and you have to dig around, read thousands of words that are not telling you the important point until you get to some fucking footnote that finally makes it clear just please don't do that, make it simple, it's simple, why complicate it? the @ syntax is good for people but it's weird for http servers
