|Subject:||(patch included) add ability to specify custom priority for HTTP::Config items|
Currently there is no way to specify a custom order for items returned from the matching method in the HTTP::Config object. I'm proposing the addition of a priority field in an item's %matchspec that is used as a sort key before using the sort key's defined by the built-in matching rules. the priority field will be treated as optional with item's not specifying it defaulting to a priority of 0. I've written a patch to introduce this functionality and uploaded it to github here:In the set of commits there is a test for the priority field, plus I updated the sorting code to correctly support the new priority field.