[continuum] BUILD FAILURE: Apache HttpComponents - HttpComponents Core - Default Maven 2 Build Definition

Online report : http://vmbuild.apache.org/continuum/buildResult.action?buildId=2111&projectId=66 Build statistics: State: Failed Previous State: Ok Started at: Tue 14 Dec 2010 03:24:23 + Finished at: Tue 14 Dec 2010 03:25:33 + Total time: 1m 9s Build Trigger: Schedule Build

Hudson build is back to normal : Htt pComponents Client » HttpClient #212

See - To unsubscribe, e-mail: dev-unsubscr...@hc.apache.org For additional commands, e-mail: dev-h...@hc.apache.org

Hudson build is back to normal : HttpComponents Client #212

See - To unsubscribe, e-mail: dev-unsubscr...@hc.apache.org For additional commands, e-mail: dev-h...@hc.apache.org

Re: Allow access to default HttpParams

On 13 December 2010 20:32, Oleg Kalnichevski wrote: > On Mon, 2010-12-13 at 16:35 +, sebb wrote: > >> == >> >> I think there should be a public method which gives access to a >> read-only copy of the parameters. >> This could either be done by: >> * changing BasicHttpParams#copyParams(HttpPara

[jira] Resolved: (HTTPCLIENT-911) Support underscore in domain name, or provide better exception

[ https://issues.apache.org/jira/browse/HTTPCLIENT-911?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sebb resolved HTTPCLIENT-911. - Resolution: Fixed Fix Version/s: (was: 4.1 Alpha2) Appears now to be fixed. > Support und

Re: Allow access to default HttpParams

On Mon, 2010-12-13 at 16:35 +, sebb wrote: > == > > I think there should be a public method which gives access to a > read-only copy of the parameters. > This could either be done by: > * changing BasicHttpParams#copyParams(HttpParams target) to be public, > in which case we probably need to

[jira] Commented: (HTTPCLIENT-911) Support underscore in domain name, or provide better exception

[ https://issues.apache.org/jira/browse/HTTPCLIENT-911?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12971022#action_12971022 ] Sebb commented on HTTPCLIENT-911: - OK, I'll remove it. It looks as though getAuthority

[jira] Commented: (HTTPCLIENT-911) Support underscore in domain name, or provide better exception

[ https://issues.apache.org/jira/browse/HTTPCLIENT-911?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12970997#action_12970997 ] Oleg Kalnichevski commented on HTTPCLIENT-911: -- Sebastian This bit of cod

[continuum] BUILD FAILURE: Apache HttpComponents - HttpComponents Client - Default Maven 2 Build Definition

Online report : http://vmbuild.apache.org/continuum/buildResult.action?buildId=2097&projectId=77 Build statistics: State: Failed Previous State: Ok Started at: Mon 13 Dec 2010 19:37:03 + Finished at: Mon 13 Dec 2010 19:37:10 + Total time: 7s Build Trigger: Schedule Build Num

Re: svn commit: r1045291 - /httpcomponents/httpclient/trunk/httpclient-cache/pom.xml

On 13 December 2010 18:51, wrote: > Author: jonm > Date: Mon Dec 13 18:51:55 2010 > New Revision: 1045291 > > URL: http://svn.apache.org/viewvc?rev=1045291&view=rev > Log: > Fixing pom (build was barfing on "--" inside an XML comment). Oops sorry - I did not notice the syntax error. > Modified:

[jira] Commented: (HTTPCLIENT-911) Support underscore in domain name, or provide better exception

[ https://issues.apache.org/jira/browse/HTTPCLIENT-911?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12970969#action_12970969 ] Sebb commented on HTTPCLIENT-911: - Unlike URI.getHost(), the determineTarget method als

[jira] Reopened: (HTTPCLIENT-911) Support underscore in domain name, or provide better exception

[ https://issues.apache.org/jira/browse/HTTPCLIENT-911?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sebb reopened HTTPCLIENT-911: - Current code does not work if there is a colon in the path but no colon in the host part. This appears

Re: Allow access to default HttpParams

On 13 December 2010 15:08, Oleg Kalnichevski wrote: > On Mon, 2010-12-13 at 11:20 +, sebb wrote: >> For HC 3.1, JMeter supports a configuration file which can be used to >> set up global defaults. >> >> There is no concept of global defaults in HC 4.x, but one can >> initialise HttpClient with

[jira] Updated: (HTTPCLIENT-1034) Add link to "Benchmarking the HttpClient Caching Module" article from Comcast Interactive Media

[ https://issues.apache.org/jira/browse/HTTPCLIENT-1034?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] matthew hawthorne updated HTTPCLIENT-1034: -- Attachment: httpclient-benchmark-doc.patch This patch includes 2 modificat

[jira] Created: (HTTPCLIENT-1034) Add link to "Benchmarking the HttpClient Caching Module" article from Comcast Interactive Media

Add link to "Benchmarking the HttpClient Caching Module" article from Comcast Interactive Media --- Key: HTTPCLIENT-1034 URL: https://issues.apache.org/jira/browse/HTTPCLI

Re: Allow access to default HttpParams

On Mon, 2010-12-13 at 11:20 +, sebb wrote: > For HC 3.1, JMeter supports a configuration file which can be used to > set up global defaults. > > There is no concept of global defaults in HC 4.x, but one can > initialise HttpClient with a DefaultedHttpParams to get similar > functionality. > >

Re: What is replacement for ClientContextConfigurer.setAuthSchemePref ?

On Mon, 2010-12-13 at 11:08 +, sebb wrote: > On 12 December 2010 18:44, Oleg Kalnichevski wrote: > > On Sun, 2010-12-12 at 15:09 +, sebb wrote: > >> ClientContextConfigurer.setAuthSchemePref is deprecated. > >> The comment says "to be replaced with a special parameter in 4.1" > >> > > > >

Build failed in Hudson: HttpCom ponents Client » HttpClient #211

See Changes: [sebb] Document initial parameter settings -- [INFO] [INF

Build failed in Hudson: HttpComponents Client #211

See Changes: [jonm] HTTPCLIENT-1032: renamed HttpCache#getVariantCacheEntries to HttpCache#getVariantCacheEntriesWithEtags and had it return a Map of etags to cache entries. Doing the filtering here makes it simpler downst

Allow access to default HttpParams

For HC 3.1, JMeter supports a configuration file which can be used to set up global defaults. There is no concept of global defaults in HC 4.x, but one can initialise HttpClient with a DefaultedHttpParams to get similar functionality. The method DefaultHttpClient.createHttpParams() creates a defa

Re: What is replacement for ClientContextConfigurer.setAuthSchemePref ?

On 12 December 2010 18:44, Oleg Kalnichevski wrote: > On Sun, 2010-12-12 at 15:09 +, sebb wrote: >> ClientContextConfigurer.setAuthSchemePref is deprecated. >> The comment says "to be replaced with a special parameter in 4.1" >> > > These parameters are AuthPNames#TARGET_AUTH_PREF and > AuthPN