##// END OF EJS Templates
hgweb: change how dispatch path is reported...
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
Gregory Szorc -
r36914:d0b0fedb default
Show More
Name Size Modified Last Commit Author
/ mercurial / thirdparty / attr
LICENSE.txt Loading ...
__init__.py Loading ...
_compat.py Loading ...
_config.py Loading ...
_funcs.py Loading ...
_make.py Loading ...
converters.py Loading ...
exceptions.py Loading ...
filters.py Loading ...
validators.py Loading ...