[
https://issues.apache.org/jira/browse/HTTPCORE-569?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary Gregory reopened HTTPCORE-569:
-----------------------------------
I am re-opening this because I need a new matcher class. The want to enforce
the order and the current implementation also is clever WRT finding a "best
match".
> 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
> Fix For: 5.0-beta7
>
>
> 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]
