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

Willem Jiang commented on CAMEL-4056:
-------------------------------------

Hi Richard,
When I run the some http test I found there are some warning like this
{code}
2011-06-09 16:19:17,272 [main           ] WARN  HttpMethodDirector             
- Required credentials not available for BASIC <any realm>@localhost:23001
2011-06-09 16:19:17,272 [main           ] WARN  HttpMethodDirector             
- Preemptive authentication requested but no default credentials available
{code}

I think it is caused by you change recently. I don't think enable  preemptive 
basic authentication by default is good idea, because in most case we don't 
need that.
Can we change the default value to be false ?


> Enable preemptive basic authentication by default
> -------------------------------------------------
>
>                 Key: CAMEL-4056
>                 URL: https://issues.apache.org/jira/browse/CAMEL-4056
>             Project: Camel
>          Issue Type: Improvement
>          Components: camel-http
>    Affects Versions: 2.7.2
>            Reporter: Richard Kettelerij
>            Assignee: Richard Kettelerij
>             Fix For: 2.8.0
>
>
> Currently Camel only sends credentials when a server explicitly prompts for 
> basic authentication. However there're cases where a URL is available to both 
> authenticated as well as unauthenticated parties. In that case the 
> {{camel-http}} component won't sent any credentials to the server, even 
> though the credentials are explicitly provided in the URI or Exchange.
> This can be solved by enabling preemptive authentication in Apache 
> HttpClient. In that case the credentials will always be provided whether the 
> server asks for it or not. Enabling this provides a sensible default.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

Reply via email to