You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hc.apache.org by "Oleg Kalnichevski (JIRA)" <ji...@apache.org> on 2014/05/23 14:55:02 UTC
[jira] [Updated] (HTTPCORE-381) Missing HttpContext in
HttpAsyncRequestHandlerMapper
[ https://issues.apache.org/jira/browse/HTTPCORE-381?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Oleg Kalnichevski updated HTTPCORE-381:
---------------------------------------
Component/s: HttpCore
Fix Version/s: Future
> Missing HttpContext in HttpAsyncRequestHandlerMapper
> ----------------------------------------------------
>
> Key: HTTPCORE-381
> URL: https://issues.apache.org/jira/browse/HTTPCORE-381
> Project: HttpComponents HttpCore
> Issue Type: Improvement
> Components: HttpCore, HttpCore NIO
> Affects Versions: 4.3.2
> Reporter: Tobias Bieniek
> Fix For: Future
>
>
> It is a common use case to use a custom HttpAsyncRequestHandlerMapper implementation to match the URLs against a list of regular expressions. Often these regular expressions include capture groups that can be used to extract parameters from the URL.
> In `/user/(\d+)/profile` for example the group can be extracted and converted to an integer. While the HttpAsyncRequestHandlerMapper implementation already does the regex matching, it has no place to save the matching results since the HttpContext is not passed to the mapper.
> The naive way to fix this is to include the HttpContext in the lookup() method interface, but unfortunately that would be a breaking change. I hope that someone is able to come up with a better solution for this.
> This issue is to some degree related to https://issues.apache.org/jira/browse/HTTPCORE-308
--
This message was sent by Atlassian JIRA
(v6.2#6252)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@hc.apache.org
For additional commands, e-mail: dev-help@hc.apache.org