[
https://issues.apache.org/jira/browse/HTTPCORE-65?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12487409
]
Roland Weber commented on HTTPCORE-65:
--------------------------------------
Hi Oleg,
that method helps for outside inspection of an HttpParams object, but it does
not solve the problem I raised. We should change the behavior of
getParameter()/getAttribute() to not return a (grand-)parent value if the local
object or one of the parents overrides with null.
An application that has a default, which is picked up for example when a
request gets executed, can use isParameterSetLocally() to determine where
exactly that parameter comes from. But knowing that the default is set on the
HttpClient level does not help to un-set it for a specific request execution.
cheers,
Roland
> Allow for explicit null in HttpContext and HttpParams
> -----------------------------------------------------
>
> Key: HTTPCORE-65
> URL: https://issues.apache.org/jira/browse/HTTPCORE-65
> Project: HttpComponents Core
> Issue Type: Improvement
> Components: HttpCore
> Affects Versions: 4.0-alpha4
> Reporter: Roland Weber
> Priority: Minor
>
> Both HttpContext and HttpParams support hierarchies. The current
> implementations ([Sync]HttpExecutionContext, BasicHttpParams) do allow for
> overriding a parent/default value with another value, but they do not allow
> for overriding with null. Implementation alternatives:
> - lookup the map entry instead of the value, do not fall back to
> parent/default if an entry is there with a null value
> - use a dedicated constant to represent an explicit null value
> cheers,
> Roland
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
