Re: [ANNOUNCEMENT] HttpComponents Client 5.0.4 GA Released

On Wed, 12 May 2021 at 17:09, Oleg Kalnichevski wrote: > > The Apache HttpComponents project is pleased to announce 5.0.4 GA > release of HttpComponents HttpClient. > > This is a maintenance release that corrects a number of defects > discovered since release 5.0.3 and upgrades HttpCore to

Incorrect heading on download page

http://hc.apache.org/downloads.cgi has the heading: HttpCore 5.1 BETA1 However the links are for BETA2 - To unsubscribe, e-mail: dev-unsubscr...@hc.apache.org For additional commands, e-mail: dev-h...@hc.apache.org

Re: String length

What are you trying to measure? On Sun, 29 Dec 2019 at 20:33, Gary Gregory wrote: > There was a PR flying around about string length and if × 2 was right or > not. But with Unicode the string length might not be the same as the > codePointCount... > so if want want to count what to put on the

Re: project-info-reports-plugin 3.0.0 - major incompatibility

On Tue, 17 Sep 2019 at 15:51, sebb wrote: > > On Tue, 17 Sep 2019 at 12:31, sebb wrote: > > > > See: > > > > http://maven.apache.org/plugins/maven-project-info-reports-plugin/#Incompatibility_Notice > > > > Maven decided to align the mojo names an

Re: project-info-reports-plugin 3.0.0 - major incompatibility

On Tue, 17 Sep 2019 at 12:31, sebb wrote: > > See: > > http://maven.apache.org/plugins/maven-project-info-reports-plugin/#Incompatibility_Notice > > Maven decided to align the mojo names and generated file names. > > This means that the report configs have to be updated

[jira] [Commented] (HTTPCORE-602) Mailing list addresses are 404

[ https://issues.apache.org/jira/browse/HTTPCORE-602?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16931508#comment-16931508 ] Sebb commented on HTTPCORE-602: --- Note that the main page http://hc.apache.org/mail-lists.html is OK

Re: [VOTE][LAZY] HttpComponents Parent 11 RC1

There does not seem to be a tag for this release. I could only find 11-RC1 Further to the email from Infra [1], [2] perhaps the tag should be created as rel/11 Sebb. [1] (original; private list) https://lists.apache.org/thread.html/6d9bc4a603214552804f4c4f8e3c7f0ae260556019b1414caf6f5825

project-info-reports-plugin 3.0.0 - major incompatibility

See: http://maven.apache.org/plugins/maven-project-info-reports-plugin/#Incompatibility_Notice Maven decided to align the mojo names and generated file names. This means that the report configs have to be updated, also the output file names have changed so direct links to the files will break.

[jira] [Reopened] (HTTPCORE-602) Mailing list addresses are 404

[ https://issues.apache.org/jira/browse/HTTPCORE-602?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sebb reopened HTTPCORE-602: --- The (un)subscribe/post links are also broken; not sure why as the pom looks OK. > Mailing list addres

Re: svn commit: r1865743 - /httpcomponents/httpasyncclient/branches/4.1.x/httpasyncclient/src/main/java/org/apache/http/impl/nio/client/PipeliningClientExchangeHandlerImpl.java

See https://issues.apache.org/jira/browse/INFRA-16738 for reason why that SVN tree was left RW On Fri, 23 Aug 2019 at 12:11, Gary Gregory wrote: > > Svn? > > Gary > > On Fri, Aug 23, 2019, 07:07 wrote: > > > Author: olegk > > Date: Fri Aug 23 11:07:41 2019 > > New Revision: 1865743 > > > > URL:

[jira] [Reopened] (HTTPCORE-534) Please delete old releases from mirroring system

[ https://issues.apache.org/jira/browse/HTTPCORE-534?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sebb reopened HTTPCORE-534: --- > Please delete old releases from mirroring sys

[jira] [Updated] (HTTPCORE-534) Please delete old releases from mirroring system

[ https://issues.apache.org/jira/browse/HTTPCORE-534?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sebb updated HTTPCORE-534: -- Issue Type: Task (was: Bug) > Please delete old releases from mirroring sys

GitHub navigation - create httpcomponents container repo?

The HC project has lots of independent Git repos. It's not particularly easy to find them all. e.g. a search for 'Apache HttpComponents' returns 55 matches. The first few entries are apache repos, but the httpcomponents-website is located after several non-ASF ones. There are another 5 pages

Re: Moin Wiki is deprecated - closing in 3 months - please migrate to Confluence

On Sat, 2 Mar 2019 at 11:19, Oleg Kalnichevski wrote: > > Folks > > We still have plenty of material on our old Wiki. Most of it looks > outdated, however. > > https://wiki.apache.org/HttpComponents/ > > I have migrated those bits I personally considered valuable to GitHub > some while ago.

Re: Duplicated sha512 links for Core 5.0-beta7 in download page

On Mon, 4 Mar 2019 at 09:38, Oleg Kalnichevski wrote: > > On Mon, 2019-03-04 at 09:02 +, sebb wrote: > > As the subject says, there are duplicated links to sha512 in: > > > > http://hc.apache.org/downloads.cgi#HttpCore_4.4.11_GA > > and > > http://hc.a

Duplicated sha512 links for Core 5.0-beta7 in download page

As the subject says, there are duplicated links to sha512 in: http://hc.apache.org/downloads.cgi#HttpCore_4.4.11_GA and http://hc.apache.org/downloads.cgi#HttpCore_5.0-beta7 - To unsubscribe, e-mail:

[jira] [Created] (HTTPCORE-534) Please delete old releases from mirroring system

Sebb created HTTPCORE-534: - Summary: Please delete old releases from mirroring system Key: HTTPCORE-534 URL: https://issues.apache.org/jira/browse/HTTPCORE-534 Project: HttpComponents HttpCore Issue

[jira] [Created] (HTTPCORE-529) MD5 should no longer be provided on download pages

Sebb created HTTPCORE-529: - Summary: MD5 should no longer be provided on download pages Key: HTTPCORE-529 URL: https://issues.apache.org/jira/browse/HTTPCORE-529 Project: HttpComponents HttpCore

[jira] [Updated] (HTTPCLIENT-1922) org.apache.http.wire package is printing sensitive information in debug

[ https://issues.apache.org/jira/browse/HTTPCLIENT-1922?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sebb updated HTTPCLIENT-1922: - Priority: Minor (was: Critical) > org.apache.http.wire package is printing sensitive informat

[jira] [Commented] (HTTPCORE-524) HTTP 2 Example uses non-existing domain

[ https://issues.apache.org/jira/browse/HTTPCORE-524?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16467475#comment-16467475 ] Sebb commented on HTTPCORE-524: --- Is the URL explicitly intended for use in such examples? If so, then I

[jira] [Commented] (HTTPCORE-524) HTTP 2 Example uses non-existing domain

[ https://issues.apache.org/jira/browse/HTTPCORE-524?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16467150#comment-16467150 ] Sebb commented on HTTPCORE-524: --- The hostname could still be provided as a parameter. That would make

[jira] [Commented] (HTTPCORE-524) HTTP 2 Example uses non-existing domain

[ https://issues.apache.org/jira/browse/HTTPCORE-524?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16467118#comment-16467118 ] Sebb commented on HTTPCORE-524: --- Why not take the host name from a command-line parameter? > HTT

[jira] [Commented] (HTTPCORE-524) HTTP 2 Example uses non-existing domain

[ https://issues.apache.org/jira/browse/HTTPCORE-524?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16457755#comment-16457755 ] Sebb commented on HTTPCORE-524: --- One needs to be very careful with including live example URLs

Travel Assistance applications for ApacheCon NA 2018 are now open!

The Travel Assistance Committee (TAC) are pleased to announce that travel assistance applications for ApacheCon NA 2018 are now open! We will be supporting ApacheCon NA Montreal, Canada on 24th - 29th September 2018 TAC exists to help those that would like to attend ApacheCon events, but are

[jira] [Commented] (HTTPCORE-511) Do not cache result of Runtime.getRuntime().availableProcessors() in IOReactorConfig

[ https://issues.apache.org/jira/browse/HTTPCORE-511?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16354441#comment-16354441 ] Sebb commented on HTTPCORE-511: --- FTR: many physical multi-cpu systems also allow CPUs to be added

Re: [DISCUSS] Migrating project website content to markdown (2nd attempt)

On 6 February 2018 at 14:31, Oleg Kalnichevski <ol...@apache.org> wrote: > On Tue, 2018-02-06 at 09:55 +0000, sebb wrote: >> On 4 February 2018 at 11:49, Oleg Kalnichevski <ol...@apache.org> >> wrote: >> > On Sat, 2018-02-03 at 23:02 +, sebb wrote: >

Re: [DISCUSS] Migrating project website content to markdown (2nd attempt)

On 6 February 2018 at 14:17, Oleg Kalnichevski wrote: > On Mon, 2018-02-05 at 23:39 -0700, Bindul Bhowmik wrote: > > ... > >> >> If I may ask as a user of the library, would the new site still have >> parts of the site that are generated from releases? For example, >> Javadocs?

Re: [DISCUSS] Migrating project website content to markdown (2nd attempt)

On 4 February 2018 at 11:49, Oleg Kalnichevski <ol...@apache.org> wrote: > On Sat, 2018-02-03 at 23:02 +0000, sebb wrote: >> On 3 February 2018 at 10:32, Oleg Kalnichevski <ol...@apache.org> > > ... > >> >> > Like, better tools tend to use markdown. >

Re: [DISCUSS] Migrating project website content to markdown (2nd attempt)

On 3 February 2018 at 10:32, Oleg Kalnichevski <ol...@apache.org> wrote: > On Sat, 2018-02-03 at 10:21 +0000, sebb wrote: >> On 2 February 2018 at 17:41, Oleg Kalnichevski <ol...@apache.org> >> wrote: >> > On Fri, 2018-02-02 at 17:05 +, sebb wrote: >

Re: [DISCUSS] Migrating project website content to markdown (2nd attempt)

On 2 February 2018 at 17:41, Oleg Kalnichevski <ol...@apache.org> wrote: > On Fri, 2018-02-02 at 17:05 +0000, sebb wrote: >> On 2 February 2018 at 13:33, Oleg Kalnichevski <ol...@apache.org> >> wrote: >> > On Wed, 2018-01-31 at 20:18 +, sebb wrote: >

Re: [DISCUSS] Migrating project website content to markdown (2nd attempt)

On 3 February 2018 at 09:31, Oleg Kalnichevski wrote: > On Fri, 2018-02-02 at 23:01 +0100, Michael Osipov wrote: >> Am 2018-01-31 um 14:06 schrieb Oleg Kalnichevski: >> > Folks >> > >> > We have a dubious honor of having absolutely the most hideous >> > project >> > web site in

Re: [DISCUSS] Migrating project website content to markdown (2nd attempt)

On 2 February 2018 at 13:33, Oleg Kalnichevski <ol...@apache.org> wrote: > On Wed, 2018-01-31 at 20:18 +0000, sebb wrote: >> It may not be pretty, but I find it legible and generally easy to >> navigate so I hope those attributes won't be lost. >> >> Also, it's

Re: [DISCUSS] Migrating project website content to markdown (2nd attempt)

It may not be pretty, but I find it legible and generally easy to navigate so I hope those attributes won't be lost. Also, it's important not to break any links. If the site is no longer built using Maven, then it may be difficult to preserve all the links (e.g. project info page links). It

Re: Old releases in https://dist.apache.org/repos/dist/release/httpcomponents

On 25 September 2017 at 14:26, Oleg Kalnichevski <ol...@apache.org> wrote: > On Sun, 2017-09-24 at 22:58 +0100, sebb wrote: >> Here are the source zips (chosen as a sample of a file that will >> appear in each release). >> > > I can update release scrip

Re: Old releases in https://dist.apache.org/repos/dist/release/httpcomponents

Here are the source zips (chosen as a sample of a file that will appear in each release). As can be seen, there are quite a few old releases. (Obviously one needs to remove more than just the src.zip!) $ svn ls -R https://dist.apache.org/repos/dist/release/httpcomponents | grep 'src\.zip$'

Re: Old releases in https://dist.apache.org/repos/dist/release/httpcomponents

On 24 September 2017 at 22:00, Oleg Kalnichevski wrote: > On Sun, 2017-09-24 at 09:26 -0600, Gary Gregory wrote: >> Hi All, >> >> We have old releases under >> https://dist.apache.org/repos/dist/release/httpcomponents >> >> I think these should be pruned to only keep the latest

Re: Jenkins and Maven builds using a different JDK

On 30 June 2017 at 00:49, sebb <seb...@gmail.com> wrote: > On 29 June 2017 at 15:51, Oleg Kalnichevski <ol...@apache.org> wrote: >> On Thu, 2017-06-29 at 13:42 +0100, sebb wrote: >>> It looks as though the Maven toolchains.xml file has been set up for &

Re: Jenkins and Maven builds using a different JDK

On 29 June 2017 at 15:51, Oleg Kalnichevski <ol...@apache.org> wrote: > On Thu, 2017-06-29 at 13:42 +0100, sebb wrote: >> It looks as though the Maven toolchains.xml file has been set up for >> most of the JDKs on Jenkins. >> > > ... > >> >>

Re: Git core repos: issues with EOLs

On 29 June 2017 at 20:55, Gary Gregory <garydgreg...@gmail.com> wrote: > On Thu, Jun 29, 2017 at 12:23 PM, sebb <seb...@gmail.com> wrote: > >> On 29 June 2017 at 20:13, Gary Gregory <garydgreg...@gmail.com> wrote: >> > Try >> > >> > git

Re: Git core repos: issues with EOLs

ith the -client repos > Gary > > On Jun 29, 2017 12:09 PM, "sebb" <seb...@gmail.com> wrote: > >> There seem to be some EOL issues with .travis.yml and README.md in >> core-master. >> >> I cloned a fresh copy (MacOSX) and git status shows changes

Git core repos: issues with EOLs

There seem to be some EOL issues with .travis.yml and README.md in core-master. I cloned a fresh copy (MacOSX) and git status shows changes: On branch master Your branch is up-to-date with 'origin/master'. Changes not staged for commit: (use "git add ..." to update what will be committed)

Jenkins and Maven builds using a different JDK

It looks as though the Maven toolchains.xml file has been set up for most of the JDKs on Jenkins. This means it should be possible to run Maven using whatever JDK version Jenkins wants - which can change - but still compile/test using a possibly different fixed JDK version. One way to to do this

[jira] [Created] (HTTPCORE-474) Difficult to find the source code repo URLs

Sebb created HTTPCORE-474: - Summary: Difficult to find the source code repo URLs Key: HTTPCORE-474 URL: https://issues.apache.org/jira/browse/HTTPCORE-474 Project: HttpComponents HttpCore Issue Type

Re: Time to give up on Java 7 compatibility? [Fwd: [JENKINS] [IMPORTANT] - Jenkins Migration and Upgrade (And JDK7 deprecation)]

On 28 June 2017 at 09:32, Oleg Kalnichevski <ol...@apache.org> wrote: > On Wed, 2017-06-28 at 00:49 +0100, sebb wrote: >> It's only Maven projects that have to be run with Java 8 on Jenkins. >> And this only affects the Maven framework. >> >> Compilation and testi

Re: Time to give up on Java 7 compatibility? [Fwd: [JENKINS] [IMPORTANT] - Jenkins Migration and Upgrade (And JDK7 deprecation)]

It's only Maven projects that have to be run with Java 8 on Jenkins. And this only affects the Maven framework. Compilation and testing can still be done with earlier Java versions. Commons has lots of components that target Java 6 or even 5, and they work fine with current Jenkins (which needs

Re: Move TrustSelfSignedStrategy and TrustAllStrategy from HttpClient 5 to HttpCore 5

On 10 May 2017 at 17:34, Gary Gregory wrote: > On Wed, May 10, 2017 at 12:49 AM, Oleg Kalnichevski > wrote: > >> On Tue, 2017-05-09 at 17:10 -0700, Gary Gregory wrote: >> > Hi All, >> > >> > I would like to move TrustSelfSignedStrategy and

Re: Git policies and practices

It would be helpful to document this on the Wiki and/or website On 10 May 2017 at 20:22, Oleg Kalnichevski wrote: > On Wed, 2017-05-10 at 21:06 +0200, Michael Osipov wrote: >> Hi folks, >> >> given that Oleg finally took up the chance migrating core and client >> to >> a

Re: Do not commit to HttpCore SVN!

If the committer squashes their commits *before* pushing then history is maintained. On 10 May 2017 at 20:16, Oleg Kalnichevski wrote: > On Wed, 2017-05-10 at 21:07 +0200, Michael Osipov wrote: >> Am 2017-05-10 um 20:52 schrieb Oleg Kalnichevski: >> > On Wed, 2017-05-10 at

Re: Checkstyle bug

You should be able to make the Javadoc work by using the full name. Indeed, I think Checkstyle is right - IMO it does not make sense to import a class purely for Javadoc purposes. It's quite useful to be able to quickly search code for an import to see where a package is used; that technique

[jira] [Updated] (HTTPCLIENT-1846) Get content decoders using the Java Service Loader mechanism

[ https://issues.apache.org/jira/browse/HTTPCLIENT-1846?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sebb updated HTTPCLIENT-1846: - Description: Get content decoders using the Java Service Loader mechanism. Current decoders

[jira] [Updated] (HTTPCORE-455) The client does not check if the IO thread is alive

[ https://issues.apache.org/jira/browse/HTTPCORE-455?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sebb updated HTTPCORE-455: -- Summary: The client does not check if the IO thread is alive (was: The client dose not check if the IO

Re: SocketConfig (v5)

On 30 March 2017 at 02:27, Gary Gregory <garydgreg...@gmail.com> wrote: > On Mar 29, 2017 5:31 PM, "sebb" <seb...@gmail.com> wrote: > > On 29 March 2017 at 21:50, Gary Gregory <garydgreg...@gmail.com> wrote: >> I really want to do this TimeV

Re: SocketConfig (v5)

e the Java 8 suits developers does not mean it suits users. There are lots of users who cannot upgrade easily (or at all) so we should not exclude them just because it is a bit easier for some devs. > Gary > > On Thu, Feb 16, 2017 at 6:47 AM, sebb <seb...@gmail.com> wrote: > &

Re: Annotations Removed in 4.5.3?

As I recall, the annotations were intended as documentation for the classes, and had class retention. So I'm not sure how this can affect 3rd party code at runtime. On 9 March 2017 at 16:07, larry mccay wrote: > Hi HC devs - > > Do I understand correctly that the

[jira] [Commented] (HTTPCLIENT-1828) HttpDelete does not extend HttpEntityEnclosingRequestBase

[ https://issues.apache.org/jira/browse/HTTPCLIENT-1828?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15893968#comment-15893968 ] Sebb commented on HTTPCLIENT-1828: -- RFC 7231 says [1]: {quote} A payload within a DELETE request

Re: SocketConfig (v5)

On 15 February 2017 at 19:10, Gary Gregory <garydgreg...@gmail.com> wrote: > On Wed, Feb 15, 2017 at 7:49 AM, sebb <seb...@gmail.com> wrote: > >> On 15 February 2017 at 05:20, Gary Gregory <garydgreg...@gmail.com> wrote: >> > I like the idea of ha

Re: SocketConfig (v5)

ps to use a different class for the setTimeout method. Would there also be a SleepTime sub-class for a pause function? > We could end up with: > > setTimeout(long, TimeUnit) > setTimeoutMillis(long) > setTimeout(Timeout) > > ? > Gary > > On Fri, Feb 10, 2017 at 4:15 PM, sebb

Re: SocketConfig (v5)

Does it make sense to use timeout units other than seconds? If not, just use [get|set]TimeoutSeconds Or if there is a need for milliseconds, then either add [get|set]TimeoutMilliSeconds or only provide that. On 10 February 2017 at 19:51, Gary Gregory wrote: > On

[jira] [Commented] (HTTPCLIENT-1812) CloseableHttpClient.execute generates SIGSEGV in jvm

[ https://issues.apache.org/jira/browse/HTTPCLIENT-1812?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15852753#comment-15852753 ] Sebb commented on HTTPCLIENT-1812: -- The SIGSEV is a JVM bug; it should not be possible for Java code

Re: [VOTE] Release HttpCore 4.4.6 based on RC1

+1 On 7 January 2017 at 14:02, Oleg Kalnichevski wrote: > Please vote on releasing these packages as HttpCore 4.4.6. > The vote is open for the at least 72 hours, and only votes from > HttpComponents PMC members are binding. The vote passes if at least > three binding +1 votes

[jira] [Commented] (HTTPCLIENT-1006) BrowserCompatSpec: don't trim " around cookie value

[ https://issues.apache.org/jira/browse/HTTPCLIENT-1006?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15795804#comment-15795804 ] Sebb commented on HTTPCLIENT-1006: -- It should be up to those wishing to challenge the status quo

Re: [VOTE] Release HttpCore 5.0-alpha2 based on RC1

Hashes sigs OK However comparison of SVN tag with httpcomponents-core-5.0-alpha2-src.tar.gz shows that some files are missing from the release tarball: .gitignore .travis.yml README.md doap_HttpComponents_Core.rdf httpcore5-testing-compat/docker/apache-httpd: .dockerignore

[jira] [Commented] (HTTPCORE-437) NullPointerException in HeaderGroup.getHeaders

[ https://issues.apache.org/jira/browse/HTTPCORE-437?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15607929#comment-15607929 ] Sebb commented on HTTPCORE-437: --- AFAICT the line that fails is: {code} if (header.getName

[jira] [Commented] (HTTPCORE-361) Please reduce object creation in HeaderGroup.getFirstHeader()

[ https://issues.apache.org/jira/browse/HTTPCORE-361?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15383146#comment-15383146 ] Sebb commented on HTTPCORE-361: --- Note: the above comments do not apply to HTTPCORE; it was auto-added

[jira] [Issue Comment Deleted] (HTTPCLIENT-1081) getMetrics() does not work for HEAD or other early release methods

[ https://issues.apache.org/jira/browse/HTTPCLIENT-1081?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sebb updated HTTPCLIENT-1081: - Comment: was deleted (was: Pattern IS thread-safe according to the class Javadoc [1] However Matcher

[jira] [Issue Comment Deleted] (HTTPCLIENT-1081) getMetrics() does not work for HEAD or other early release methods

[ https://issues.apache.org/jira/browse/HTTPCLIENT-1081?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sebb updated HTTPCLIENT-1081: - Comment: was deleted (was: Github user PascalSchumacher commented on a diff in the pull request

[jira] [Commented] (HTTPCLIENT-1081) getMetrics() does not work for HEAD or other early release methods

[ https://issues.apache.org/jira/browse/HTTPCLIENT-1081?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15383012#comment-15383012 ] Sebb commented on HTTPCLIENT-1081: -- Pattern IS thread-safe according to the class Javadoc [1

[jira] [Issue Comment Deleted] (HTTPCLIENT-1081) getMetrics() does not work for HEAD or other early release methods

[ https://issues.apache.org/jira/browse/HTTPCLIENT-1081?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sebb updated HTTPCLIENT-1081: - Comment: was deleted (was: Github user sebbASF commented on a diff in the pull request: https

Re: [VOTE] Release HttpAsyncClient 4.1.2 based on RC1

On 14 June 2016 at 09:46, Oleg Kalnichevski wrote: > On Mon, 2016-06-13 at 14:22 -0700, Gary Gregory wrote: >> On Mon, Jun 13, 2016 at 10:16 AM, Oleg Kalnichevski >> wrote: > > ... > >> > Gary >> > Could you please add this line prior to the assert (See patch

Re: BasicAsyncResponseConsumer needs OOM protection?

On 3 June 2016 at 19:45, Oleg Kalnichevski wrote: > On Thu, 2016-06-02 at 19:35 +, Idzerda, Edan wrote: >> > -Original Message- >> > From: Oleg Kalnichevski [mailto:ol...@apache.org] >> > Sent: Tuesday, May 31, 2016 3:04 PM >> > To: HttpComponents Project

[jira] [Commented] (HTTPCLIENT-923) NetscapeDraftSpec is too strict about cookie expires date format

[ https://issues.apache.org/jira/browse/HTTPCLIENT-923?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15304071#comment-15304071 ] Sebb commented on HTTPCLIENT-923: - JIRA is not a support forum. Please subscribe to the HttpClient

[jira] [Commented] (HTTPCLIENT-1742) No connection reuse if response is compressed

[ https://issues.apache.org/jira/browse/HTTPCLIENT-1742?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15280830#comment-15280830 ] Sebb commented on HTTPCLIENT-1742: -- The change to drop the headers has caused a regression

Re: HttpCore - CC buddy license.

On 2 March 2016 at 22:19, Justi Kd wrote: > Legal response: > "The CC-BY license is on the category B license, which means it should be > prominently labelled and as a separate binary file (for example a jar file). > This is so it's clear to users that it's in there (which

Re: HttpCore - CC buddy license.

On 29 February 2016 at 22:13, Justi Kd wrote: >> What we could do is replace @Immutable, @ThreadSafe and @NonThreadSafe >> with a single annotation, say, @Threading with three values Safe, >> NonSafe and Immutable and drop @GuardedBy altogether. > > > > That looks like a good

[jira] [Commented] (HTTPCLIENT-1610) Stale connections in pool cause NoHttpResponseException

[ https://issues.apache.org/jira/browse/HTTPCLIENT-1610?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15132159#comment-15132159 ] Sebb commented on HTTPCLIENT-1610: -- You are comparing the release notes for httpcore

Re: Better header API

On 30 November 2015 at 21:43, Michael Osipov wrote: > Am 2015-11-30 um 19:53 schrieb Gary Gregory: >> >> I mean: >> >> Index: src/main/java/org/apache/hc/core5/http/HttpMessage.java >> === >> ---

Re: Re: Re: HC 5.0: package / module structure; Re: HC 5.0: co-location with HC 4.x

On 23 November 2015 at 09:46, Michael Osipov <1983-01...@gmx.net> wrote: >> On Mon, 2015-11-23 at 10:08 +0100, Michael Osipov wrote: >> > > On Sun, Nov 22, 2015 at 3:10 PM, Jon Moore wrote: >> > > >> > > > On Sat, Nov 21, 2015 at 1:56 PM, Michael Osipov >> >

Re: HC 5.0: co-location with HC 4.x

On 19 November 2015 at 21:17, Michael Osipov wrote: > Am 2015-11-19 um 12:32 schrieb Oleg Kalnichevski: >> >> Folks >> >> I would like to start working on the first alpha releases of HC 5.0. >> >> There is one issue that still needs to be discussed though before I can >>

Re: HC 5.0: co-location with HC 4.x

On 19 November 2015 at 11:32, Oleg Kalnichevski wrote: > Folks > > I would like to start working on the first alpha releases of HC 5.0. > > There is one issue that still needs to be discussed though before I can > proceed. We need to decide on how we intent to maintain

[jira] [Commented] (HTTPCORE-412) Send HTTP trailers in request

[ https://issues.apache.org/jira/browse/HTTPCORE-412?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14996370#comment-14996370 ] Sebb commented on HTTPCORE-412: --- bq. I cannot return empty array If a method can return null, it can just

[jira] [Commented] (HTTPCORE-412) Send HTTP trailers in request

[ https://issues.apache.org/jira/browse/HTTPCORE-412?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14995837#comment-14995837 ] Sebb commented on HTTPCORE-412: --- Unless you need to distinguish between "trailers not yet gene

[jira] [Commented] (HTTPCLIENT-1692) Apache HttpClient overrides the protocols supplied by JVM and instead defaults it to TLSv1.0

[ https://issues.apache.org/jira/browse/HTTPCLIENT-1692?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14995864#comment-14995864 ] Sebb commented on HTTPCLIENT-1692: -- Please can you provide a code sample that shows the problem you

Re: [ANNOUNCEMENT] HttpComponents Core 4.4.4 GA released

@olegk Looks like that part of the website was not updated as part of r1711465 The download page is part of the main site, not the components On 8 November 2015 at 01:12, sebb <seb...@gmail.com> wrote: > OK, I see now; 4.4.4 is not (yet) listed on the page. > > On 8 November 201

Re: Draft board report for November 2015

On 4 November 2015 at 08:57, Oleg Kalnichevski wrote: > On Wed, 2015-11-04 at 06:57 +0530, Asankha C. Perera wrote: >> Hi All >> >> Please take a moment to check the draft for the next board meeting. I >> have currently kept the date for HttpComponents Core 4.4.4 open as its >>

[jira] [Commented] (HTTPCORE-410) PoolStats should implement Serializable

[ https://issues.apache.org/jira/browse/HTTPCORE-410?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14950585#comment-14950585 ] Sebb commented on HTTPCORE-410: --- Serialisation is tricky to get right, and has to be maintained

Re: svn commit: r1697563 - /httpcomponents/contrib/httpcore/trunk/pom.xml

On 25 August 2015 at 06:57, ggreg...@apache.org wrote: Author: ggregory Date: Tue Aug 25 05:57:49 2015 New Revision: 1697563 URL: http://svn.apache.org/r1697563 Log: Replace 4.0-alpha5-SNAPSHOT with 4.4.1. Log message does not agree with the change Modified:

[jira] [Commented] (HTTPCLIENT-1677) Update Apache Commons from 1.9 to 1.10.

[ https://issues.apache.org/jira/browse/HTTPCLIENT-1677?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14710453#comment-14710453 ] Sebb commented on HTTPCLIENT-1677: -- What is Apache Commons? i.e. what component

[jira] [Commented] (HTTPCLIENT-1664) Migrate away from Commons Logging to SLF4J

[ https://issues.apache.org/jira/browse/HTTPCLIENT-1664?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14612970#comment-14612970 ] Sebb commented on HTTPCLIENT-1664: -- Note that Commons Logging does support

[jira] [Commented] (HTTPCLIENT-1664) Migrate away from Commons Logging to SLF4J

[ https://issues.apache.org/jira/browse/HTTPCLIENT-1664?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14613054#comment-14613054 ] Sebb commented on HTTPCLIENT-1664: -- +1 to Oleg's suggestion. If you decide to take

[jira] [Commented] (HTTPCLIENT-1664) Migrate away from Commons Logging to SLF4J

[ https://issues.apache.org/jira/browse/HTTPCLIENT-1664?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14611822#comment-14611822 ] Sebb commented on HTTPCLIENT-1664: -- 1) Commons Logging has not been updated

[jira] [Commented] (HTTPCLIENT-1664) Migrate away from Commons Logging to SLF4J

[ https://issues.apache.org/jira/browse/HTTPCLIENT-1664?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14611983#comment-14611983 ] Sebb commented on HTTPCLIENT-1664: -- The classloader issues are dealt with here

[jira] [Commented] (HTTPCLIENT-1664) Migrate away from Commons Logging to SLF4J

[ https://issues.apache.org/jira/browse/HTTPCLIENT-1664?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14612863#comment-14612863 ] Sebb commented on HTTPCLIENT-1664: -- I've updated the Tomcat reference in the Wiki

Re: [VOTE] Release HttpComponents Client 4.5 based on RC2

On 31 May 2015 at 12:54, Oleg Kalnichevski ol...@apache.org wrote: Please vote on releasing these packages as HttpComponents Client 4.5. The vote is open for the at least 72 hours, and only votes from HttpComponents PMC members are binding. The vote passes if at least three binding +1 votes

Re: [VOTE] Release HttpComponents Core 4.4.1 based on RC1

On 14 March 2015 at 16:50, Oleg Kalnichevski ol...@apache.org wrote: Please vote on releasing these packages as HttpComponents Core 4.4.1. The vote is open for the at least 72 hours, and only votes from HttpComponents PMC members are binding. The vote passes if at least three binding +1 votes

[jira] [Commented] (HTTPCLIENT-1621) Possible NPE/incorrect type in HttpClientBuilder#evictIdleConnections

[ https://issues.apache.org/jira/browse/HTTPCLIENT-1621?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14340519#comment-14340519 ] Sebb commented on HTTPCLIENT-1621: -- Autoboxing applies at compilation time, so

Re: Assigning issues

On 27 February 2015 at 19:52, Michael Osipov micha...@apache.org wrote: Am 2015-02-27 um 11:28 schrieb Oleg Kalnichevski: On Thu, 2015-02-26 at 21:16 +0100, Michael Osipov wrote: Oleg, is there any reason why you don't assign issues to yourself if you planning to fix/already fixed them?

[jira] [Updated] (HTTPCLIENT-1582) SSPI-based auth might fail if output token size is too small

[ https://issues.apache.org/jira/browse/HTTPCLIENT-1582?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sebb updated HTTPCLIENT-1582: - Description: It might happen that a user has many groups, this makes the output token bigger

[jira] [Updated] (HTTPCLIENT-1582) SSPI-based auth might fail if output token size is too small

[ https://issues.apache.org/jira/browse/HTTPCLIENT-1582?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sebb updated HTTPCLIENT-1582: - Summary: SSPI-based auth might fail if output token size is too small (was: SSPI-based atuh might

[jira] [Commented] (HTTPCLIENT-1613) DefaultHostNameVerifier fails matching wildcard in subject alt name

[ https://issues.apache.org/jira/browse/HTTPCLIENT-1613?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14323028#comment-14323028 ] Sebb commented on HTTPCLIENT-1613: -- What API needs to be changed? Is it not just

[jira] [Commented] (HTTPCLIENT-1613) DefaultHostNameVerifier fails matching wildcard in subject alt name

[ https://issues.apache.org/jira/browse/HTTPCLIENT-1613?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14323085#comment-14323085 ] Sebb commented on HTTPCLIENT-1613: -- OK, that's useful to know. The problem here

  1   2   3   4   5   6   7   8   9   10   >