comparison .hgtags @ 36898:d0b0fedbfb53

hgweb: change how dispatch path is reported When I implemented the new request object, I carried forward some ugly hacks until I could figure out what was happening. One of those was the handling of PATH_INFO to determine how to route hgweb requests. Essentially, if we have PATH_INFO data, we route according to that. But if we don't, we route by the query string. I question if we still need to support query string routing. But that's for another day, I suppose. In this commit, we clean up the ugly "havepathinfo" hack and replace it with a "dispatchpath" attribute that can hold None or empty string to differentiate between the presence of PATH_INFO. This is still a bit hacky. But at least the request parsing and routing code is explicit about the meaning now. Differential Revision: https://phab.mercurial-scm.org/D2820
author Gregory Szorc <gregory.szorc@gmail.com>
date Sun, 11 Mar 2018 13:38:56 -0700
parents 2034cf3bfc70
children 61f6cee88940
comparison
equal deleted inserted replaced
36897:d7fd203e36cc 36898:d0b0fedbfb53