[ 
https://issues.apache.org/jira/browse/HTTPCORE-569?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16762472#comment-16762472
 ] 

Oleg Kalnichevski commented on HTTPCORE-569:
--------------------------------------------

[~garydgregory] Works for me. You might want to add some unit tests though. 

Please when merging the branch use {{--no-ff}} option, so the merge operation 
would produce a merge record in the commit history. Alternatively once you are 
happy with the branch I can merge it for you.

Oleg
 

> Create new value in org.apache.hc.core5.http.protocol.UriPatternType to 
> lookup without an exact match override
> --------------------------------------------------------------------------------------------------------------
>
>                 Key: HTTPCORE-569
>                 URL: https://issues.apache.org/jira/browse/HTTPCORE-569
>             Project: HttpComponents HttpCore
>          Issue Type: New Feature
>          Components: HttpCore
>            Reporter: Gary Gregory
>            Assignee: Gary Gregory
>            Priority: Major
>
> Create new value in {{org.apache.hc.core5.http.protocol.UriPatternType}} to 
> lookup values without an exact match override: This allows path matches 
> _without_ having an exact match override the order in which the patterns are 
> defined (which is the current behavior.)
> This is a request from some of my users at work, they just want to a list of 
> URI patterns in a specific order which is observed no matter what. Very handy 
> for testing.
> The implementation would refactor {{UriPatternMatcher}} to allow a boolean to 
> be passed in.
> I created branch {{HTTPCORE-569}} with a proposal.
> You use this by calling 
> {{org.apache.hc.core5.http.impl.bootstrap.AsyncServerBootstrap.setUriPatternType(UriPatternType)}}.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to