You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@hc.apache.org by ol...@apache.org on 2021/02/15 16:48:59 UTC
[httpcomponents-website] branch master updated (02f7d1e -> c7f55b1)
This is an automated email from the ASF dual-hosted git repository.
olegk pushed a change to branch master
in repository https://gitbox.apache.org/repos/asf/httpcomponents-website.git.
from 02f7d1e Set `ignorePathsToDelete` to include components only; updated legacy, DEV and GA component links
new 6ccab64 Migrated project content to Markdown
new c7f55b1 Common redirects
The 2 revisions listed above as "new" are entirely new to this
repository and will be described in separate emails. The revisions
listed as "add" were already present in the repository and have only
been added to this reference.
Summary of changes:
src/site/apt/charter.apt | 165 -----
src/site/apt/get-involved.apt | 61 --
src/site/apt/index.apt | 95 ---
src/site/apt/mail.apt | 262 -------
src/site/apt/news.apt | 1467 -------------------------------------
src/site/apt/poweredby.apt | 88 ---
src/site/apt/status.apt | 84 ---
src/site/markdown/charter.md | 134 ++++
src/site/markdown/get-involved.md | 65 ++
src/site/markdown/index.md | 60 ++
src/site/markdown/mail.md | 190 +++++
src/site/markdown/news.md | 1215 ++++++++++++++++++++++++++++++
src/site/markdown/status.md | 84 +++
src/site/resources/.htaccess | 6 +
src/site/site.xml | 1 -
15 files changed, 1754 insertions(+), 2223 deletions(-)
delete mode 100644 src/site/apt/charter.apt
delete mode 100644 src/site/apt/get-involved.apt
delete mode 100644 src/site/apt/index.apt
delete mode 100644 src/site/apt/mail.apt
delete mode 100644 src/site/apt/news.apt
delete mode 100644 src/site/apt/poweredby.apt
delete mode 100644 src/site/apt/status.apt
create mode 100644 src/site/markdown/charter.md
create mode 100644 src/site/markdown/get-involved.md
create mode 100644 src/site/markdown/index.md
create mode 100644 src/site/markdown/mail.md
create mode 100644 src/site/markdown/news.md
create mode 100644 src/site/markdown/status.md
create mode 100644 src/site/resources/.htaccess
[httpcomponents-website] 02/02: Common redirects
Posted by ol...@apache.org.
This is an automated email from the ASF dual-hosted git repository.
olegk pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/httpcomponents-website.git
commit c7f55b173c0f13f04d827dd21d5ba24aec8feaf1
Author: Oleg Kalnichevski <Ol...@abraxas.ch>
AuthorDate: Mon Feb 15 17:48:36 2021 +0100
Common redirects
---
src/site/resources/.htaccess | 6 ++++++
1 file changed, 6 insertions(+)
diff --git a/src/site/resources/.htaccess b/src/site/resources/.htaccess
new file mode 100644
index 0000000..c1bd396
--- /dev/null
+++ b/src/site/resources/.htaccess
@@ -0,0 +1,6 @@
+Redirect permanent "/httpclient-3.x" "/httpclient-legacy"
+Redirect permanent "/httpcomponents-asyncclient-ga" "/httpcomponents-asyncclient-4.1.x"
+Redirect temp "/httpcomponents-core-ga" "/httpcomponents-core-5.0.x"
+Redirect temp "/httpcomponents-client-ga" "/httpcomponents-client-5.0.x"
+Redirect temp "/httpcomponents-core-dev" "/httpcomponents-core-5.1.x"
+Redirect temp "/httpcomponents-client-dev" "/httpcomponents-client-5.1.x"
[httpcomponents-website] 01/02: Migrated project content to Markdown
Posted by ol...@apache.org.
This is an automated email from the ASF dual-hosted git repository.
olegk pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/httpcomponents-website.git
commit 6ccab64d6a72b480ec8d856ca2916cf54b9df9b3
Author: Oleg Kalnichevski <Ol...@abraxas.ch>
AuthorDate: Mon Feb 15 17:40:29 2021 +0100
Migrated project content to Markdown
---
src/site/apt/charter.apt | 165 -----
src/site/apt/get-involved.apt | 61 --
src/site/apt/index.apt | 95 ---
src/site/apt/mail.apt | 262 -------
src/site/apt/news.apt | 1467 -------------------------------------
src/site/apt/poweredby.apt | 88 ---
src/site/apt/status.apt | 84 ---
src/site/markdown/charter.md | 134 ++++
src/site/markdown/get-involved.md | 65 ++
src/site/markdown/index.md | 60 ++
src/site/markdown/mail.md | 190 +++++
src/site/markdown/news.md | 1215 ++++++++++++++++++++++++++++++
src/site/markdown/status.md | 84 +++
src/site/site.xml | 1 -
14 files changed, 1748 insertions(+), 2223 deletions(-)
diff --git a/src/site/apt/charter.apt b/src/site/apt/charter.apt
deleted file mode 100644
index 3e095c3..0000000
--- a/src/site/apt/charter.apt
+++ /dev/null
@@ -1,165 +0,0 @@
-~~ ====================================================================
-~~ Licensed to the Apache Software Foundation (ASF) under one
-~~ or more contributor license agreements. See the NOTICE file
-~~ distributed with this work for additional information
-~~ regarding copyright ownership. The ASF licenses this file
-~~ to you under the Apache License, Version 2.0 (the
-~~ "License"); you may not use this file except in compliance
-~~ with the License. You may obtain a copy of the License at
-~~
-~~ http://www.apache.org/licenses/LICENSE-2.0
-~~
-~~ Unless required by applicable law or agreed to in writing,
-~~ software distributed under the License is distributed on an
-~~ "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
-~~ KIND, either express or implied. See the License for the
-~~ specific language governing permissions and limitations
-~~ under the License.
-~~ ====================================================================
-~~
-~~ This software consists of voluntary contributions made by many
-~~ individuals on behalf of the Apache Software Foundation. For more
-~~ information on the Apache Software Foundation, please see
-~~ <http://www.apache.org/>.
-
- ----------
- HttpComponents Project Charter
- ----------
- ----------
- ----------
-
-~~ The Charter was approved by a PMC vote ending on 2008-02-09.
-~~ Changes to the Charter require PMC approval.
-~~ DO NOT EDIT the "Charter" section, not even to fix typos.
-
-{Charter}
-
- The Apache HttpComponents project is responsible for creating and
- maintaining a toolset of low level Java components focused on HTTP
- and associated protocols.
-
- We develop and maintain a component called <<HttpCore>>, which addresses
- the basic needs for communicating via HTTP on the client and server side.
- HttpCore defines a framework for extending the provided functionality
- beyond the basic needs.
-
- We develop and maintain a component called <<HttpClient>>, which builds
- on HttpCore and adds functionality typically required for client-side
- HTTP communication. In particular, HttpClient adds support for cookies,
- authentication, and client-side connection management.
-
- <<HttpCore>> and <<HttpClient>> are at the center of the
- Apache HttpComponents project. All other activities orbit around this duo.
-
- We maintain the codebase of the Jakarta Commons HttpClient, also known as
- Commons HttpClient 3.1, until such time that the new HttpClient based on
- HttpCore is considered ready for use in production systems.
-
- We are looking for new components that build upon and extend the
- functionality of the existing ones.
- We are also looking for new components that complement the
- functionality of the existing ones and make them more useful
- or easier to use.
-
- We are open to give a home to applications that derive a significant part
- of their functionality from our components, if approached by such projects.
-
-~~
-~~ end of the "Charter" section that must not be edited without PMC approval
-~~
-
-
-{History}
-
- The history of the HttpComponents starts with the now retired
- {{{http://jakarta.apache.org/slide/}Jakarta Slide}} project.
- Slide was a WebDAV server including a client component, and the
- WebDAV protocol builds on HTTP. There was interest in using the
- client-side HTTP implementation independently of Slide.
- The code was spun off from Slide in 2001 to become the HttpClient
- subproject of the Jakarta Commons.
-
- Since it generated a disproportional amount of traffic on the
- Commons mailing lists, HttpClient activity was moved to separate
- mailing lists. This started the dissociation of HttpClient from
- Commons, which continued when HttpClient was promoted to the
- Jakarta subproject level in 2004.
- The latter event is recorded as the oldest {{{./news.html}News}} item
- of the HttpComponents project.
-
- The shortcomings in the design of HttpClient, as explained in the
- {{{./commons-httpclient-lessons.html}Lessons Learned}},
- created interest in redesigning the API from scratch. To that end, the
- Jakarta HttpComponents project replaced the HttpClient project in 2005.
- The new project was charged with the tasks of developing a successor
- to HttpClient 3.x, and of maintaining the existing codebase until the
- new one is ready to take over.
-
- The {{{http://commons.apache.org/}Commons}}, cradle of HttpClient,
- left Jakarta in 2007 to become an independent Top Level Project.
- Later in the same year, the HttpComponents project also left Jakarta
- to become an independent Top Level Project, taking the responsibility
- for maintaining HttpClient 3.x with it.
- Our TLP resolution is presented below.
-
-
-{Resolution}
-
- The Apache HttpComponents project was established
- as an Apache top level project in November 2007,
- when the Apache Board approved the following resolution:
-
-~~ The following is a verbatim copy of the TLP resolution.
-~~ DO NOT EDIT, not even to fix typos
-------------------------------
-Establish the Apache HttpComponents project
-
-WHEREAS, the Board of Directors deems it to be in the best interests of the Foundation and
-consistent with the Foundation's purpose to establish a Project Management Committee charged with
-the creation and maintenance of open-source software related to a toolset of low level Java
-components focused on HTTP and associated protocols, and of applications based on these components,
-for distribution at no charge to the public.
-
-NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee (PMC), to be known as "Apache
-HttpComponents Project", be and hereby is established pursuant to Bylaws of the Foundation; and be
-it further
-
-RESOLVED, that the Apache HttpComponents Project be and hereby is responsible for the creation and
-maintenance of a toolset of low level Java components focused on HTTP and associated protocols, and
-of applications based on these components; and be it further
-
-RESOLVED, that the office of "Vice President, Apache HttpComponents" be and hereby is created, the
-person holding such office to serve at the direction of the Board of Directors as the chair of the
-Apache HttpComponents Project, and to have primary responsibility for management of the projects
-within the scope of responsibility of the Apache HttpComponents Project; and be it further
-
-RESOLVED, that the persons listed immediately below be and hereby are appointed to serve as the
-initial members of the Apache HttpComponents Project:
-
- * Oleg Kalnichevski <olegk AT apache DOT org>
- * Sebastian Bazley <sebb AT apache DOT org>
- * Erik Abele <erikabele AT apache DOT org>
- * Ortwin Gl�ck <oglueck AT apache DOT org>
- * Roland Weber <rolandw AT apache DOT org>
- * Ant Elder <antelder AT apache DOT org>
- * Paul Fremantle <pzf AT apache DOT org>
- * Asankha Perera <asankha AT apache DOT org>
-
-NOW, THEREFORE, BE IT FURTHER RESOLVED, that Erik Abele be appointed to the office of Vice
-President, Apache HttpComponents, to serve in accordance with and subject to the direction of the
-Board of Directors and the Bylaws of the Foundation until death, resignation, retirement, removal or
-disqualification, or until a successor is appointed; and be it further
-
-RESOLVED, that the Apache HttpComponents Project be and hereby is tasked with the migration and
-rationalization of the Apache Jakarta HttpComponents subproject; and be it further
-
-RESOLVED, that the Apache HttpComponents Project be and hereby is tasked with the migration and
-maintenance of the codebase formerly known as Apache Jakarta Commons HttpClient until it is
-obsoleted by the components of the Apache HttpComponents Project; and be it further
-
-RESOLVED, that all responsibilities pertaining to the Apache Jakarta HttpComponents subproject and
-the former Apache Jakarta Commons HttpClient codebase encumbered upon the Apache Jakarta Project are
-hereafter discharged.
-------------------------------
-
-
diff --git a/src/site/apt/get-involved.apt b/src/site/apt/get-involved.apt
deleted file mode 100644
index 208c3f3..0000000
--- a/src/site/apt/get-involved.apt
+++ /dev/null
@@ -1,61 +0,0 @@
-~~ ====================================================================
-~~ Licensed to the Apache Software Foundation (ASF) under one
-~~ or more contributor license agreements. See the NOTICE file
-~~ distributed with this work for additional information
-~~ regarding copyright ownership. The ASF licenses this file
-~~ to you under the Apache License, Version 2.0 (the
-~~ "License"); you may not use this file except in compliance
-~~ with the License. You may obtain a copy of the License at
-~~
-~~ http://www.apache.org/licenses/LICENSE-2.0
-~~
-~~ Unless required by applicable law or agreed to in writing,
-~~ software distributed under the License is distributed on an
-~~ "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
-~~ KIND, either express or implied. See the License for the
-~~ specific language governing permissions and limitations
-~~ under the License.
-~~ ====================================================================
-~~
-~~ This software consists of voluntary contributions made by many
-~~ individuals on behalf of the Apache Software Foundation. For more
-~~ information on the Apache Software Foundation, please see
-~~ <http://www.apache.org/>.
-
- -----------
- Get Involved With HttpComponents
-
-Community
-
- * Users mailing list: {{{mailto:httpclient-users@hc.apache.org}httpclient-users@}} for general discussion, questions, and announcements. This is the perfect place to ask for help if you need it!
-
- * Development mailing list: {{{mailto:dev@hc.apache.org}dev@}} for discussion about project development.
-
- * GitHub: Star us at {{{https://github.com/apache/httpcomponents-core/}apache/httpcomponents-core}} and {{{https://github.com/apache/httpcomponents-client/}apache/httpcomponents-client}} and use this to follow HttpComponents development or contribute pull requests. If you're interested in development, please see the Contributing section below for details on our development process.
-
- * Reporting issues:
-
- * {{{https://issues.apache.org/jira/projects/HTTPCORE}HttpComponents Core}}
-
- * {{{https://issues.apache.org/jira/projects/HTTPCLIENT}HttpComponents Client}} and {{{https://issues.apache.org/jira/projects/HTTPASYNC}HttpComponents AsyncClient}}
-
- * Slack: Some committers and users are present in the channel {{{https://the-asf.slack.com/archives/CGC9KPJKH}#httpcomponents-client}} on the Apache Slack team.
-
- * StackOverflow: While the user mailing list is the primary resource for asking questions, if you prefer StackOverflow, make sure to tag your question with {{{https://stackoverflow.com/questions/tagged/apache-httpcomponents}apache-httpcomponents}}.
-
-Contributing
-
- HttpComponents is a community-led project and we are delighted to receive contributions of anything from minor fixes to new features.
- If you have an itch to scratch, then by all means do that! Fixing bugs you run into, or adding features you need, are both immensely helpful.
- There are plenty of ways to help outside writing code. Code review of pull requests (even if you are not a committer), feature suggestions, reporting bugs, documentation and usability feedback all matter immensely.
-
-Testing
-
- All Pull Requests are automatically tested on {{{https://travis-ci.com/apache/httpcomponents-core}Travis CI (Core)}}, {{{https://travis-ci.com/apache/httpcomponents-client}Travis CI (Client)}} on both AMD64 and ARM64 architectures.
-
-More information
-
- As it happens, the ways to get involved into an open source project are basically the same for all projects.
- Please have a look at the {{{http://incubator.apache.org/guides/participation.html}Incubator Guide To Participation}}.
- It's terse, but has pointers to additional information elsewhere at Apache.
- The sections on participating as a User and as a Developer apply here, too.
diff --git a/src/site/apt/index.apt b/src/site/apt/index.apt
deleted file mode 100644
index 67ede9d..0000000
--- a/src/site/apt/index.apt
+++ /dev/null
@@ -1,95 +0,0 @@
-~~ ====================================================================
-~~ Licensed to the Apache Software Foundation (ASF) under one
-~~ or more contributor license agreements. See the NOTICE file
-~~ distributed with this work for additional information
-~~ regarding copyright ownership. The ASF licenses this file
-~~ to you under the Apache License, Version 2.0 (the
-~~ "License"); you may not use this file except in compliance
-~~ with the License. You may obtain a copy of the License at
-~~
-~~ http://www.apache.org/licenses/LICENSE-2.0
-~~
-~~ Unless required by applicable law or agreed to in writing,
-~~ software distributed under the License is distributed on an
-~~ "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
-~~ KIND, either express or implied. See the License for the
-~~ specific language governing permissions and limitations
-~~ under the License.
-~~ ====================================================================
-~~
-~~ This software consists of voluntary contributions made by many
-~~ individuals on behalf of the Apache Software Foundation. For more
-~~ information on the Apache Software Foundation, please see
-~~ <http://www.apache.org/>.
-
- ----------
- Apache HttpComponents
- ----------
- ----------
- ----------
-
-Apache HttpComponents
-
- The Apache HttpComponents\u2122 project is responsible for creating and maintaining a toolset of
-low level Java components focused on HTTP and associated protocols.
-
- This project functions under the Apache Software Foundation (http://www.apache.org), and is part
-of a larger community of developers and users.
-
-HttpComponents Overview
-
- The Hyper-Text Transfer Protocol (HTTP) is perhaps the most significant protocol used on the
- Internet today. Web services, network-enabled appliances and the growth of network computing
- continue to expand the role of the HTTP protocol beyond user-driven web browsers, while
- increasing the number of applications that require HTTP support.
-
- Designed for extension while providing robust support for the base HTTP protocol, the
- HttpComponents may be of interest to anyone building HTTP-aware client and server
- applications such as web browsers, web spiders, HTTP proxies, web service transport
- libraries, or systems that leverage or extend the HTTP protocol for distributed communication.
-
-{HttpComponents Structure}
-
-* {HttpComponents Core}
-
- {{{./httpcomponents-core-ga/index.html}HttpCore}} is a set of low level HTTP transport components
- that can be used to build custom client and server side HTTP services with a minimal footprint.
- HttpCore supports two I/O models: blocking I/O model based on the classic Java I/O and
- non-blocking, event driven I/O model based on Java NIO.
-
- The blocking I/O model may be more appropriate for data intensive, low latency scenarios,
- whereas the non-blocking model may be more appropriate for high latency scenarios where raw data
- throughput is less important than the ability to handle thousands of simultaneous HTTP
- connections in a resource efficient manner.
-
- * HttpCore Tutorial {{{./httpcomponents-core-ga/tutorial/html}HTML}}
- / {{{./httpcomponents-core-ga/tutorial/pdf/httpcore-tutorial.pdf}PDF}}
-
- * HttpCore {{{./httpcomponents-core-ga/examples.html}Examples}}
-
-* {HttpComponents Client}
-
- {{{./httpcomponents-client-ga/index.html}HttpClient}} is a HTTP/1.1 compliant HTTP agent
- implementation based on HttpCore. It also provides reusable components for client-side
- authentication, HTTP state management, and HTTP connection management. HttpComponents Client
- is a successor of and replacement for {{{http://hc.apache.org/httpclient-legacy/index.html}
- Commons HttpClient 3.x}}. Users of Commons HttpClient are strongly encouraged to upgrade.
-
- * HttpClient Tutorial {{{./httpcomponents-client-ga/tutorial/html}HTML}}
- / {{{./httpcomponents-client-ga/tutorial/pdf/httpclient-tutorial.pdf}PDF}}
-
- * HttpClient {{{./httpcomponents-client-ga/examples.html}Samples}}
-
-* {HttpComponents AsyncClient}
-
- {{{./httpcomponents-asyncclient-dev/index.html}Asynch HttpClient}} is a HTTP/1.1 compliant HTTP agent
- implementation based on HttpCore NIO and HttpClient components. It is a complementary module
- to Apache HttpClient intended for special cases where ability to handle a great number of
- concurrent connections is more important than performance in terms of a raw data throughput.
-
- * HttpAsyncClient {{{./httpcomponents-asyncclient-dev/examples.html}Samples}}
-
-* {Commons HttpClient (legacy)}
-
- Commons HttpClient 3.x codeline is at the end of life. All users of Commons HttpClient 3.x
- are strongly encouraged to upgrade to HttpClient 4.1.
diff --git a/src/site/apt/mail.apt b/src/site/apt/mail.apt
deleted file mode 100644
index cfcee65..0000000
--- a/src/site/apt/mail.apt
+++ /dev/null
@@ -1,262 +0,0 @@
-~~ ====================================================================
-~~ Licensed to the Apache Software Foundation (ASF) under one
-~~ or more contributor license agreements. See the NOTICE file
-~~ distributed with this work for additional information
-~~ regarding copyright ownership. The ASF licenses this file
-~~ to you under the Apache License, Version 2.0 (the
-~~ "License"); you may not use this file except in compliance
-~~ with the License. You may obtain a copy of the License at
-~~
-~~ http://www.apache.org/licenses/LICENSE-2.0
-~~
-~~ Unless required by applicable law or agreed to in writing,
-~~ software distributed under the License is distributed on an
-~~ "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
-~~ KIND, either express or implied. See the License for the
-~~ specific language governing permissions and limitations
-~~ under the License.
-~~ ====================================================================
-~~
-~~ This software consists of voluntary contributions made by many
-~~ individuals on behalf of the Apache Software Foundation. For more
-~~ information on the Apache Software Foundation, please see
-~~ <http://www.apache.org/>.
-
- -----------
- HttpComponents Mailing Lists
-
-{About Mailing Lists}
-
- A mailing list is an electronic discussion forum that you can subscribe to.
- Once you are subscribed, you will receive every email that is sent to the
- list, and you can send mails to the list yourself. Every mail you send
- there will be received by hundreds, maybe thousands of subscribers.
- It will also become available in public archives indefinitely.
-
- Please note that usage of these mailing lists is subject to the
- {{{http://www.apache.org/foundation/public-archives.html}Public Forum Archive Policy}}
-
- <<Please>> take a few minutes to read this page, in order to avoid
- annoyance for other subscribers, and embarrassment for yourself.
- There is a common set of etiquette guidelines for internet forums,
- sometimes called <netiquette>. You should be aware of these and
- try to observe them, here as well as in other forums.
-
- Eric S. Raymond and Rick Moen have written an article called
- {{{http://www.catb.org/~esr/faqs/smart-questions.html}
- "How To Ask Questions The Smart Way"}}
- about mailing list netiquette. It's a long read, but worth the effort.
- \
- <<Note:>> Please do NOT send your HttpComponents questions to the two
- authors. They welcome feedback on the article itself, but are simply
- not a help resource for HttpComponents.
-
-
-{Research First}
-
- Before you post a question to a mailing list, make sure it isn't
- already answered. Read the available documentation. Search the web,
- and in particular the mailing list archives. Being answered with a
- link to a mail or FAQ entry that addresses exactly your question
- is one of the embarrassments you should avoid.
- \
- If you are answered with a link to a mail, don't take it too hard either.
- Maybe you didn't know the correct terms to search for, or the mail was
- sent on another list. People that follow a mailing list for a long time
- are bound to remember some of the old mails, and it may be easier for
- them to locate the old mail than to write down the answer again.
-
-
-{Choose The Appropriate Forum}
-
- Different kinds of questions are discussed in different forums.
- It is important to choose the right forum for your question.
- Posting a question to the wrong forum reduces your chances of
- getting a useful response. You will reach fewer people that can
- answer your question, and those that could will be less inclined
- to do so.
- \
- <<Do not cross-post.>> Do not send your question to more than one list.
- If you are in doubt where to post your question, it is better to pick
- the wrong list than to send it to several lists. Even if you get answers
- on more than one list, people subscribed to only one list will not be able
- to follow the whole discussion. Mailing list archives will also contain
- only fragments of the discussion, so that it becomes harder for others
- with the same question to find the answer.
-
- The article mentioned above has a section called
- {{{http://www.catb.org/~esr/faqs/smart-questions.html#forum}
- "Choose your forum carefully"}}.
- It basically tells you the same stuff you'll find below.
-
-* {User List}
-
- If you develop an application that <<uses>> HttpClient, and you need
- advice on how to achieve something with it, post your question to the
- <<httpclient-users>> list.
- If you don't know whether HttpClient can do what you want it to do,
- post your question to the users list.
- Even though you are a developer, you are not a developer of the
- HttpComponents. So please don't post your question to the developer list.
- \
- And if somebody else asks a question you can answer, please do so!
-
-* {Developer List}
-
- If you want to discuss <<development of HttpComponents>>, post your
- question or suggestion to the <<dev>> list. The developer list is used
- to discuss architecture, API design, new features, and bugs.
- Bug reports and comments filed in {{{./issue-tracking.html}JIRA}} will
- automatically be sent to this list, too.
-
-* {Issue Tracking}
-
- We are using {{{./issue-tracking.html}JIRA}} as our issue tracking system.
- Although this is not a mailing list, and should not be abused as a general
- discussion forum, it is another way to contact the HttpComponent developers.
- All issues and comments will be sent to the developer mailing list.
- \
- If you are absolutely sure that you have found a bug, you can open a
- new issue for it. Choose "Bug" as the issue type.
- If you are absolutely sure that our components don't provide a feature
- that would be useful for you and others, you can open a new issue for it.
- Choose "New Feature" or "Wish" for it.
- \
- If you are not absolutely sure, please ask on the appropriate mailing list
- first. Most developers are monitoring both lists, and we will tell you
- if you should open a new issue.
-
-* {Personal Mail}
-
- <<Never>> send a question directly to one of the people you have seen
- active on the mailing lists, or whose email address you've found in
- the source code. You will be scorned and rebuffed, or at best ignored.
- \
- HttpComponents, as any other Apache project, is a <community>.
- Questions asked on a mailing list can be answered by any member of the
- community who knows the answer and has the time to write it down.
- Answers sent to a mailing list are available to everyone, through the
- public mailing list archives. This benefits the whole community.
- \
- By sending a question directly to somebody, you are implying that this
- person alone is responsible for helping you out, and only you.
- No, we're not. We participate in a community.
- Post your question to the community at large, and chances are that one
- of the members will answer it.
- If that requires information that is of little interest to the community,
- for example large log files, you will be <asked> to send such information
- directly to the person that picked up your question.
- \
- It's OK to send a "Thank You" mail to a person that helped you.
- Just make sure that your next question goes to the mailing list again.
-
-
-{Shape Your Mail}
-
- Some of the people reading your mail will be processing dozens or hundreds
- of mails daily. To get their attention and a quick reply, it is important
- that you make your mail easy to read and that you provide the background
- information that is needed to answer your question.
- The biggest part of the article on
- {{{http://www.catb.org/~esr/faqs/smart-questions.html}
- asking smart questions}}
- mentioned above addresses this problem, so we'll only give you the
- highlights here.
-
- * <<Choose a descriptive Subject>> for your mail. Not:
- \
- "Help! URGENT: Problem with HttpClient!!!"
- \
- This subject does not give the least indication of what your mail is about.
- So you have a problem with HttpClient? And you need help?
- Duh, why else would you post to the mailing list.
- And it's urgent? For you maybe, but not for anyone else here.
-
- * <<Don't send HTML mail>>, or other stylized mails.
- Use plain text. Either format it with about 72 characters per line, or
- just type without linebreaks so automatic formatters can take care of it.
- Don't format your mails with 90 characters per line. Automatic formatters
- will split each line, making the result very hard to read.
-
-
- * <<Get to the point.>>
- Ideally, keep your mail short. Just describe the problem and give the
- necessary background information. If it's read in less than a minute,
- many people will read it and the answer can probably be given quickly
- as well. If it takes several minutes to read your mail, people will
- take care of other mails first, and may never bother to read yours.
- If you have to provide extensive background information, make sure to
- get to the point in the first paragraph. The one that can be read in
- less than a minute. Describe your problem there, so people can decide
- quickly whether it makes sense for them to read the rest.
-
- * <<Don't Reply to send a new question.>>
- If you have an answer or otherwise want to join an ongoing discussion,
- then use Reply-To on another mail.
- If you have a new question or want to start a new discussion, do not reply
- to a mail you've received from the list. Even if you change the subject,
- your mail client would still flag it as belonging to the existing thread.
- Many archives and email clients provide a threaded view, where only the
- initial mail of a thread is shown by default. Your mail will just get
- ignored by the people not interested in the original thread, even though
- they might be able to help you.
-
-
-{The Lists}
-
- The HttpComponents project currently uses the following lists.
- Clicking on a list name will take you to a page with subscribe,
- unsubscribe, and archive information.
- See below for information on <digests>.
-
- * {{{./mail-lists.html}httpclient-users}} -
- The list for users of HttpClient, either version 3 or 4.
- Users of HttpCore can also post their questions here, although
- most subscribers will probably not be able to answer them.
-
- * {{{./mail-lists.html}dev}} -
- The list for developers of HttpComponents and HttpClient 3.
- We don't mind getting HttpCore user questions here.
- Our issues tracker JIRA also posts here.
-
- * {{{./mail-lists.html}commits}} -
- The list for messages from our source code repository. Whenever the
- source code is modified, a mail with the changes is sent.
- This list is read-only.
- HttpComponents committers are expected to subscribe to the commits list, so
- they can review the changes.
-
- * <private> -
- The list for private communication of the HttpComponents PMC.
- Only PMC members and ASF members can subscribe.
- There is no public archive.
-
-{Subscribe And Unsubscribe}
-
- To subscribe to the list "<xxx>", send a mail to
- "<xxx>-subscribe@hc.apache.org".
- While you are subscribed, you will receive all mails sent to the list.
- You can send mails to the list yourself using the address
- "<xxx>@hc.apache.org". This does not apply for the commits list,
- where only the source code repository is allowed to send mails.
-
- To unsubscribe from the list "<xxx>", send a mail to
- "<xxx>-unsubscribe@hc.apache.org".
- Unsubscribe information is also appended to every mail sent via the list.
-
- The <<digest>> of a list collects all mails of that list, sending you
- occasional updates. Each update contains the subjects of the recent mails,
- and the mails themselves as attachments. This significantly reduces the
- number of individual mails you receive from the list, while still giving
- you access to all the information.
-
- To subscribe to the digest of list "<xxx>", send a mail to
- "<xxx>-digest-subscribe@hc.apache.org".
- While you are subscribed to the digest, you can send mails to the
- list itself using the address
- "<xxx>@hc.apache.org". This does not apply for the commits list,
- where only the source code repository is allowed to send mails.
-
- To unsubscribe from the digest of list "<xxx>", send a mail to
- "<xxx>-digest-unsubscribe@hc.apache.org".
- Unsubscribe information is also appended to every mail sent by the digest.
diff --git a/src/site/apt/news.apt b/src/site/apt/news.apt
deleted file mode 100644
index e1ecace..0000000
--- a/src/site/apt/news.apt
+++ /dev/null
@@ -1,1467 +0,0 @@
-~~ ====================================================================
-~~ Licensed to the Apache Software Foundation (ASF) under one
-~~ or more contributor license agreements. See the NOTICE file
-~~ distributed with this work for additional information
-~~ regarding copyright ownership. The ASF licenses this file
-~~ to you under the Apache License, Version 2.0 (the
-~~ "License"); you may not use this file except in compliance
-~~ with the License. You may obtain a copy of the License at
-~~
-~~ http://www.apache.org/licenses/LICENSE-2.0
-~~
-~~ Unless required by applicable law or agreed to in writing,
-~~ software distributed under the License is distributed on an
-~~ "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
-~~ KIND, either express or implied. See the License for the
-~~ specific language governing permissions and limitations
-~~ under the License.
-~~ ====================================================================
-~~
-~~ This software consists of voluntary contributions made by many
-~~ individuals on behalf of the Apache Software Foundation. For more
-~~ information on the Apache Software Foundation, please see
-~~ <http://www.apache.org/>.
-
- ----------
- HttpComponents News
- ----------
- ----------
- ----------
-
-HttpComponents Project News
-
-* 12 February 2021 - HttpComponents Client 5.1-beta1 released
-
- This is the first BETA release in the 5.1 release series that includes a number of
- new features as well performance optimizations in the classic HTTP transport.
-
- Notable changes and features included in the 5.1 series:
-
- * Conditional conformance with RFC 3986 (Uniform Resource Identifier (URI):
- Generic Syntax).
-
- * Improved support for out of sequence response message handing by the the classic
- (blocking) HTTP transport.
-
-
-* 8 February 2021 - HttpComponents Core 5.1-beta3 released
-
- This is likely the last BETA release in the 5.1 release series. The next release is
- expected to be 5.1 GA. This beta includes a number of new features as well as
- bug fixes from the stable 5.0.x branch.
-
- Notable changes and features included in the 5.1 series:
-
- * Conditional conformance with RFC 3986 (Uniform Resource Identifier (URI):
- Generic Syntax).
-
- * Improved support for out of sequence response message handing by the the classic
- (blocking) HTTP transport.
-
-* 3 December 2020 - HttpComponents Core 5.1-beta2 released
-
- This is the second BETA release in the 5.1 release series that includes a number of
- new features as well as bug fixes from the stable 5.0.x branch.
-
-
-* 3 December 2020 - HttpComponents Core 5.0.3 (GA) released
-
- This is a maintenance release that corrects a number of defects discovered since
- release 5.0.2 including a defect in the async (non-blocking) transport potentially
- causing an infinite event loop and and excessive CPU utilization.
-
-
-* 1 December 2020 - HttpComponents Core 4.4.14 (GA) released
-
- This is a maintenance release that corrects a number of defects discovered since release 4.4.13
- including two defects in the async (non-blocking) transport potentially causing an infinite
- event loop and and excessive CPU utilization.
-
-
-* 8 October 2020 - HttpComponents Client 5.0.3 (GA) released
-
- This is a maintenance release that fixes incorrect handling of malformed authority component
- in request URIs.
-
-
-* 8 October 2020 - HttpComponents Client 4.5.13 (GA) released
-
- This is a maintenance release that fixes incorrect handling of malformed authority component
- in request URIs.
-
-
-* 28 September 2020 - HttpComponents Client 5.0.2 (GA) released
-
- This is a maintenance release that upgrades HttpCore to the latest version and addresses
- a number of issues found since 5.0.1 release.
-
-
-* 21 September 2020 - HttpComponents Core 5.1-beta1 released
-
- This is the first BETA release in the 5.1 release series that includes a number of
- new features as well performance optimizations in the classic HTTP transport.
-
-
-* 13 September 2020 - HttpComponents Core 5.0.2 (GA) released
-
- This release reverts changes to early response handling logic introduced in 5.0.1
- and fixes a number of minor defects. Improvement of the early response handling
- by the classic client protocol handler has been moved to 5.1.
-
-
-* 15 June 2020 - HttpComponents Client 5.0.1 (GA) released
-
- This is a maintenance release that upgrades HttpCore to the latest version and addresses
- a number of issues found since 5.0 release.
-
-
-* 10 June 2020 - HttpComponents Core 5.0.1 (GA) released
-
- This is a maintenance release that improves handling of early response messages by
- the classic client protocol handler and fixes a number of minor defects.
-
-
-* 9 March 2020 - HttpComponents Client 4.5.12 (GA) released
-
- This is a maintenance release that fixes a regression introduced by the previous release
- that caused rejection of certificates with non-standard domains.
-
-
-* 24 February 2020 - HttpComponents Client 5.0 (GA) released
-
- This is the first stable (GA) release of HttpClient 5.0.
-
- Notable changes and features included in the 5.0 series are:
-
- * Support for the HTTP/2 protocol and conformance to requirements and
- recommendations of the latest HTTP/2 protocol specification documents
- (RFC 7540, RFC 7541.)
-
- Supported features:
-
- * HPACK header compression
-
- * Stream multiplexing (client and server)
-
- * Flow control
-
- * Response push
-
- * Message trailers
-
- * Expect-continue handshake
-
- * Connection validation (ping)
-
- * Application-layer protocol negotiation (ALPN)
-
- * TLS 1.2 security features
-
- * Improved conformance to requirements and recommendations of the latest HTTP/1.1 protocol
- specification documents (RFC 7230, RFC 7231.)
-
- * New connection pool implementation with lax connection limit guarantees and better
- performance under higher concurrency due to absence of a global pool lock.
-
- * Support for Reactive Streams API [http://www.reactive-streams.org/]
-
- * Package name space changed to 'org.apache.hc.client5'.
-
- * Maven group id changed to 'org.apache.httpcomponents.client5'.
-
- HttpClient 5.0 releases can be co-located with earlier major versions on the same classpath
- due to the change in package names and Maven module coordinates.
-
-
-* 18 February 2020 - HttpComponents Core 5.0 (GA) released
-
- This is the first stable (GA) release of HttpCore 5.0.
-
- Notable changes and features included in the 5.0 series:
-
- * Support for HTTP/2 protocol and conformance to requirements and recommendations
- of the latest HTTP/2 protocol specification (RFC 7540, RFC 7541)
-
- Supported features:
-
- * HPACK header compression
-
- * stream multiplexing (client and server)
-
- * flow control
-
- * response push (client and server)
-
- * message trailers
-
- * expect-continue handshake
-
- * connection validation (ping)
-
- * application-layer protocol negotiation (ALPN) on Java 9+
-
- * TLS 1.2 security features
-
- Features out of scope for 5.0 release:
-
- * padding of outgoing frames
-
- * stream priority
-
- * plain connection HTTP/1.1 upgrade
-
- * CONNECT method
-
- * Improved conformance to requirements and recommendations of the latest HTTP/1.1 protocol
- specification (RFC 7230, RFC 7231)
-
- * New asynchronous HTTP transport APIs consistent for both HTTP/1.1 and HTTP/2 transport.
-
- * Redesigned I/O reactor APIs and improved NIO based reactor implementation for a greater
- performance and scalability.
-
- * Support for server-side request filters for classic and asynchronous server implementations.
- Request filters could be used to implement cross-cutting protocol aspects such
- as the 'expect-continue' handshaking and user authentication / authorization.
-
- * Support for Reactive Streams API [http://www.reactive-streams.org/]
-
- * Redesigned connection pool implementation with strict connection limit guarantees.
- The connection pool is expected to have a better performance under higher concurrency
- due to reduced global pool lock contention.
-
- * New connection pool implementation with lax connection limit guarantees and better
- performance under higher concurrency due to absence of a global pool lock.
-
- * Package name space changed to 'org.apache.hc.core5'
-
- * Maven group id changed to 'org.apache.httpcomponents.core5'
-
-
-* 27 January 2020 - HttpComponents Client 5.0-beta7 released
-
- This BETA release upgrades HttpCore to the latest version and addresses a number of issues found
- since the previous BETA release.
-
-* 20 January 2020 - HttpComponents Client 4.5.11 (GA) released
-
- This is a maintenance release that fixes a number defects discovered since 4.5.10
- and upgrades HttpCore dependency to version 4.4.13.
-
-* 14 January 2020 - HttpComponents Core 4.4.13 (GA) released
-
- This is a maintenance release that corrects a number of defects discovered since
- release 4.4.12.
-
-* 8 January 2019 - HttpComponents HttpCore 5.0-beta11 released
-
- This BETA fixes HTTP/2 SETTINGS_HEADER_TABLE_SIZE negotiation and HTTP/2 connection window
- management logic as well as fixes a number of other defects found since the last release.
-
-* 31 October 2019 - HttpComponents HttpCore 5.0-beta10 released
-
- This BETA fixes a bug in the HTTP/2 setting handshake implementation and a performance
- regression in HTTP/1.1 protocol handler.
-
-
-* 10 October 2019 - HttpComponents HttpClient 5.0-beta6 released
-
- This BETA release picks up the latest fixes and performance improvements from HttpCore
- and addresses a number of issues found since the previous BETA release.
-
-* 7 October 2019 - HttpComponents HttpCore 5.0-beta9 released
-
- This BETA fixes a number of defects found since the last release, improves behavior
- of the lax (concurrent) connection pools, simplifies and improves input event handling
- of SSL/TLS sessions and the HTTP/1.1 protocol event handler.
-
-
-* 10 Sept 2019 - HttpComponents Client 4.5.10 (GA) released
-
- This is a maintenance release that corrects a number of defects discovered since
- release 4.5.9.
-
-* 5 Sept 2019 - HttpComponents Core 4.4.12 (GA) released
-
- This is a maintenance release that corrects a number of defects discovered since
- release 4.4.11.
-
-* 22 July 2019 - HttpComponents HttpClient 5.0-beta5 released
-
- This BETA release picks up the latest fixes and performance improvements from
- HttpCore and addresses a number of issues found since the previous BETA release.
-
-* 15 July 2019 - HttpComponents HttpCore 5.0-beta8 released
-
- This BETA fixes a number of defects found since the last release and adds several
- convenience factory and builder classes, mainly for TLS configuration and HTTP
- message construction.
-
- Notable new features in this release:
-
- * As of this version all server and requester implementations exclude weak TLS protocol
- versions and ciphers.
-
-
-* 12 June 2019 - HttpComponents HttpClient 4.5.9 (GA) released
-
- This is a maintenance release that fixes a number defects discovered since 4.5.8.
-
-* 8 April 2019 - HttpComponents HttpClient 5.0-beta4 released
-
- This BETA release picks up the latest fixes and performance improvements from HttpCore
- and addresses a number of issues found since the previous BETA release.
-
- Notable features in this release:
-
- * Security improvements.
-
- * URI handling improvements.
-
-* 31 March 2019 - HttpComponents HttpClient 4.5.8 (GA) released
-
- This is a maintenance release that makes request URI normalization configurable on
- per request basis and also ports several improvements in URI handling from HttpCore
- master.
-
-* 4 March 2019 - HttpComponents HttpCore 5.0-beta7 released
-
- This BETA release adds support for SOCKS version 5, improves support for TLS
- handshake timeout configuration, improves URI builder, and fixes various defects.
-
- Notable new features in this release:
-
- * SOCKS version 5 support
-
- * Improved TLS handshake timeout configuration
-
-* 24 January 2019 - HttpComponents HttpClient 4.5.7 (GA) released
-
- This is a maintenance release that corrects Automatic-Module-Name definitions added in
- the previous release and fixes a number of minor defects discovered since 4.5.6.
-
-* 21 January 2019 - HttpComponents HttpCore 4.4.11 (GA) released
-
- This is a maintenance release that corrects a number of defects in non-blocking SSL
- session code that caused compatibility issues with TLSv1.3 protocol implementation
- shipped with Java 11.
-
-* 17 December 2018 - HttpComponents HttpClient 5.0-beta3 released
-
- This BETA release adds support for advanced TLS functions (such as ALPN protocol negotiation)
- on Java 1.7 and Java 1.8 through Conscrypt TLS library and picks up the latest fixes
- and performance improvements from HttpCore.
-
- Notable new features in this release:
-
- * TLS ALPN protocol negotiation support on older JREs through Conscrypt TLS library.
-
-
-* 6 December 2018 - HttpComponents HttpCore 5.0-beta6 released
-
- This BETA release adds support for advanced TLS functions (such as ALPN protocol negotiation)
- on Java 1.7 and Java 1.8 through Conscrypt TLS library, and fixes a number of defects found
- since the previous release.
-
- Notable new features in this release:
-
- * TLS ALPN protocol negotiation on Java 1.7 and Java 1.8 through Conscrypt TLS library
-
-
-* 29 October 2018 - HttpComponents HttpClient 5.0-beta2 released
-
- This BETA release resolves compatibility issues with Java 11 new TLS engine as well as
- a number of defects found since the previous release.
-
- Notable new features in this release:
-
- * JDK 11 compatibility
-
- * Support for request specific push consumers
-
- * Support for Reactive Streams API [http://www.reactive-streams.org/]
-
-
-* 22 October 2018 - HttpComponents HttpCore 5.0-beta5 released
-
- This BETA release adds support for Reactive Streams API [http://www.reactive-streams.org/]
- and fixes compatibility issues with Java 11 new TLS engine as well as a number of defects
- found since the previous release.
-
- This release also includes a redesigned HTTP stress test tool loosely based on
- Apache Benchmark (AB) command interface with support for HTTP/2.
-
-
-* 29 August 2018 - HttpComponents HttpCore 5.0-beta3 released
-
- This BETA release fixes a number of defects found since the previous release, adds several
- incremental improvements and improves javadoc documentation.
-
-* 23 July 2018 - HttpComponents HttpAsyncClient 4.1.4 (GA) released
-
- This is a maintenance release that adds Automatic-Module-Name to the manifest
- for compatibility with Java 9 Platform Module System and fixes a number of issues
- discovered since 4.1.3.
-
-* 9 July 2018 - HttpComponents HttpClient 4.5.6 (GA) released
-
- This is a maintenance release that adds Automatic-Module-Name to the manifest
- for compatibility with Java 9 Platform Module System and fixes a number of issues
- discovered since 4.5.5.
-
-* 3 July 2018 - HttpComponents HttpCore 4.4.10 (GA) released
-
- This is a maintenance release that adds Automatic-Module-Name to the manifest
- for compatibility with Java 9 Platform Module System and fixes a number of issues
- discovered since 4.4.9.
-
-* 22 January 2018 - HttpComponents HttpClient 4.5.5 GA released
-
- This is a maintenance release that fixes a regression introduced
- by the previous release causing a NPE in SystemDefaultCredentialsProvider.
-
-* 18 January 2018 - HttpComponents HttpClient 5.0-beta1 released
-
- This is the first BETA release of HttpClient 5.0. The 5.0 release serices introduces
- support for the HTTP/2 protocol and event driven messaging APIs consistent for all
- supported HTTP protocol versions.
-
- HttpClient ships with two client implementations:
-
- * HttpClient Classic is based on the classic (blocking) I/O model; largely compatible
- with the 4.x APIs; supports HTTP/1.1 only.
-
- * HttpClient Async is based on NIO model; new event driven APIs consistent for all supported
- HTTP protocol versions; supports both HTTP/1.1 and HTTP/2.
-
- []
-
- Notable new features in this release:
-
- * New asynchronous HTTP cache backend APIs
-
- * Fully asynchronous HTTP cache backend based on Memcached
-
- * Support for bulk cache retrieval
-
-* 15 January 2018 - HttpComponents HttpCore 5.0-beta2 released
-
- This BETA release fixes a number of defects found since the previous release and
- adds several incremental improvements.
-
-* 11 January 2018 - HttpComponents HttpCore 4.4.9 (GA) released
-
- This is a maintenance release that fixes a number of issues discovered since 4.4.8 and adds a few low-level methods.
-
-* 4 December 2017 - HttpComponents HttpClient 4.5.4 (GA) released
-
- This is a maintenance release that fixes a number of issues discovered since release 4.5.3.
-
-* 27 November 2017 - HttpComponents HttpClient 5.0-alpha3 released
-
- This is a major release that introduces support for the HTTP/2 protocol and event driven
- messaging APIs consistent for all supported HTTP protocol versions.
-
- Notable new features in this release:
-
- * Asynchronous HttpClient implementations optimized for HTTP/2 multiplexed request execution.
-
- * Full support for HTTP caching by asynchronous HttpClient implementations including
- streaming message exchanages.
-
-* 6 November 2017 - HttpComponents HttpCore 5.0-beta1 released
-
- This is a major release that renders HttpCore API incompatible with the stable 4.x branch
- and upgrades HTTP/1.1 and HTTP/2 protocol conformance to the requirements and recommendations
- of the latest protocol specification.
-
- Notable new features in this release:
-
- * New HTTP/2 requester optimized for multiplexed execution of requests.
-
-* 7 October 2017 - HttpComponents HttpCore 4.4.8 (GA) released
-
- This is a maintenance release that fixes a number of issues discovered since release 4.4.7.
-
-* 14 September 2017 - HttpComponents HttpCore 4.4.7 (GA) released
-
- This is a maintenance release that fixes a number of issues discovered since release 4.4.6.
-
-* 4 September 2017 - HttpComponents HttpCore 5.0-alpha4 released
-
- This is a major release that renders HttpCore API incompatible with the stable 4.x branch
- and upgrades HTTP/1.1 and HTTP/2 protocol conformance to the requirements and recommendations
- of the latest protocol specification.
-
-* 11 May 2017 - HttpComponents HttpClient 5.0-alpha2 released
-
- This is a major release that introduces support for HTTP/2 protocol and event driven
- messaging APIs consistent for all supported HTTP protocol versions.
-
-* 2 May 2017 - HttpComponents HttpCore 5.0-alpha3 released
-
- This is a major release that renders HttpCore API incompatible with the stable 4.x branch
- and upgrades HTTP/1.1 and HTTP/2 protocol conformance to the requirements and recommendations
- of the latest protocol specification.
-
-* 10 February 2017 - HttpComponents HttpAsyncClient 4.1.3 (GA) released
-
- This is a maintenance release that fixes a number of issues discovered since release 4.1.2.
-
-* 27 January 2017 - HttpComponents HttpClient 4.5.3 (GA) released
-
- This is a maintenance release that fixes a number of issues discovered since release 4.5.2.
-
-* 12 January 2017 - HttpComponents HttpCore 4.4.6 (GA) released
-
- This is a maintenance release that fixes a number of issues discovered since release 4.4.5.
-
-* 27 December 2016 - HttpComponents HttpCore 5.0-alpha2 released
-
- This is a major release that renders HttpCore API incompatible with the stable 4.x branch
- and upgrades HTTP/1.1 and HTTP/2 protocol conformance to the requirements and recommendations
- of the latest protocol specification.
-
-* 27 June 2016 - HttpComponents HttpAsyncClient 4.1.2 (GA) released
-
- This is a maintenance release that fixes a number of issues discovered since release 4.1.1.
-
-* 14 June 2016 - HttpComponents HttpCore 4.4.5 (GA) released
-
- This is a maintenance release that fixes a number of issues discovered since release 4.4.4.
-
-* 1 March 2016 - HttpComponents HttpClient 4.5.2 (GA) released
-
- This is a maintenance release that fixes a number of minor bugs reported since 4.5.1.
-
-* 28 January 2016 - HttpComponents HttpClient 5.0-alpha1 released
-
- This is a major release that renders HttpClient API incompatible with the stable 4.x branch
- and upgrades HTTP/1.1 protocol conformance to the requirements and recommendations of
- the latest protocol specification. This release lays the foundation for transition to HTTP/2
- as the primary transport protocol in the future releases.
-
-* 3 January 2016 - HttpComponents HttpCore 5.0-alpha1 released
-
- This is a major release that renders HttpCore API incompatible with the stable 4.x branch
- and upgrades HTTP/1.1 protocol conformance to the requirements and recommendations of the
- latest protocol specification. This release lays the foundation for transition to HTTP/2 as
- the primary transport protocol in the future releases.
-
-* 9 November 2015 - HttpComponents HttpAsyncClient 4.1.1 (GA) released
-
- This is a maintenance release that fixes a number of issues discovered since release 4.1 and
- upgrades HttpCore and HttpClient dependencies.
-
-* 4 November 2015 - HttpComponents HttpCore 4.4.4 (GA) released
-
- This is a maintenance release that fixes a number of issues discovered since release 4.4.3.
-
-* 16 September 2015 - HttpComponents HttpClient 4.5.1 (GA) released
-
- This is a maintenance release that fixes a number of minor bugs reported since 4.5.
-
-* 11 September 2015 - HttpComponents HttpCore 4.4.3 (GA) released
-
- This maintenance release fixes a bug in non-blocking HTTP request pipelining code discovered
- since 4.3.1.
-
-* 5 June 2015 - HttpClient 4.5 (GA) released
-
- HttpClient 4.5 (GA) is a minor feature release that includes several incremental enhancements
- to the exisitng functionality such as support for private domains in the Mozilla Public Suffix
- List.
-
-* 23 April 2015 - HttpAsyncClient 4.1 (GA) released
-
- This is the first stable (GA) release of HttpAsyncClient 4.1. Notable features and enhancements
- included in 4.1 series are:
-
- * Support for pipelined request execution
-
- * Support for the latest HTTP state management specification (RFC 6265). Please note that the
- old cookie policy is still used by default for compatibility reasons. RFC 6265 compliant cookie
- policies need to be explicitly configured by the user. Please also note that as of next feature
- release support for Netscape draft, RFC 2109 and RFC 2965 cookie policies will be deprecated
- and disabled by default. It is recommended to use RFC 6265 compliant policies for new
- applications unless compatibility with RFC 2109 and RFC 2965 is required and to migrate
- existing applications to the default cookie policy.
-
- * Enhanced, redesigned and rewritten default SSL hostname verifier with improved RFC 2818
- compliance
-
- * Default SSL hostname verifier and default cookie policy now validate certificate identity
- and cookie domain of origin against the public suffix list maintained by Mozilla.org
- <https://publicsuffix.org/list>
-
- * Authentication cache thread-safety: authentication cache used by HttpClient is now
- thread-safe and can be shared by multiple threads in order to re-use authentication state for
- subsequent requests
-
-* 31 March 2015 - HttpComponents HttpClient 4.4.1 (GA) released
-
- This is a maintenance release that fixes a number of bugs reported since 4.4.
-
-* 20 March 2015 - HttpComponents HttpCore 4.4.1 (GA) released
-
- This is a maintenance release that fixes a number of minor bugs found since 4.4.
-
-* 5 February 2015 - HttpComponents HttpClient 4.4 released
-
- This is the first stable (GA) release of HttpClient 4.4. Notable features and enhancements
- included in 4.4 series are:
-
- * Support for the latest HTTP state management specification (RFC 6265). Please note that the
- old cookie policy is still used by default for compatibility reasons. RFC 6265 compliant cookie
- policies need to be explicitly configured by the user. Please also note that as of next feature
- release support for Netscape draft, RFC 2109 and RFC 2965 cookie policies will be deprecated
- and disabled by default. It is recommended to use RFC 6265 compliant policies for new
- applications unless compatibility with RFC 2109 and RFC 2965 is required and to migrate
- existing applications to the default cookie policy.
-
- * Enhanced, redesigned and rewritten default SSL hostname verifier with improved RFC 2818
- compliance
-
- * Default SSL hostname verifier and default cookie policy now validate certificate identity
- and cookie domain of origin against the public suffix list maintained by Mozilla.org
- <https://publicsuffix.org/list>
-
- * More efficient stale connection checking: indiscriminate connection checking which results
- in approximately 20 to 50 ms overhead per request has been deprecated in favor of conditional
- connection state validation (persistent connections are to be re-validated only if a specified
- period inactivity has elapsed)
-
- * Authentication cache thread-safety: authentication cache used by HttpClient is now thread-safe
- and can be shared by multiple threads in order to re-use authentication state for subsequent
- requests
-
- * Native Windows Negotiate and NTLM via SSPI through JNA: when running on Windows OS HttpClient
- configured to use native NTLM or SPNEGO authentication schemes can make use of platform specific
- functionality via JNA and current user credentials. This functionality is still considered
- experimental, known to have compatibility issues and subject to change without prior notice.
-
-* 17 December 2014 - HttpComponents HttpCore 4.4 released
-
- This is the first stable (GA) release of HttpCore 4.4. The most notable features included in
- 4.4 series are:
-
- * Support for pipelined request processing on the server side
-
- * Support for pipelined request execution on the client side
-
- * Simplified bootstrapping of blocking and non-blocking (NIO) HTTP server implementations
-
- * Inclusion of SSL context initialization utilities from HttpClient
-
-* 6 November 2014 - HttpComponents HttpClient 4.3.6 (GA) released
-
- This is a maintenance release that fixes several problems with HttpClient OSGi bundle as well
- as some other issues reported since release 4.3.5.
-
- Please note that as of this release HttpClient disables all versions of SSL (including SSLv3)
- in favor of the TLS protocol by default. Those users who wish to continue using SSLv3 need
- to explicitly enable support for it.
-
-* 22 October 2014 - HttpComponents HttpCore 4.3.3 (GA) released
-
- This maintenance release fixes a number of bugs found since 4.3.2, mostly in the NIO transport
- components. All users of HttpCore 4.3 are advised to upgrade.
-
-* 17 October 2014 - HttpComponents HttpAsyncClient 4.4-beta1 released
-
- This is the first BETA release of HttpAsyncClient 4.1. Notable features and enhancements
- included in 4.1 series are:
-
- * Support for pipelined request execution
-
- * Enhanced redesigned and rewritten default SSL hostname verifier with improved RFC 2818
- compliance
-
- * Default SSL hostname verifier and default cookie policy now validate certificate identity
- and cookie domain of origin against the public suffix list maintained by Mozilla.org
- <https://publicsuffix.org/list>
-
- * Authentication cache thread-safety: authentication caches used by HttpAsyncClient is now
- thread-safe and can be shared by multiple contexts in order to re-use authentication state for
- subsequent requests
-
-* 28 September 2014 - HttpComponents HttpClient 4.4-beta1 released
-
- This is the first BETA release of HttpClient 4.4. Notable features and enhancements included
- in 4.4 series are: enhanced redesigned and rewritten default SSL hostname verifier with
- improved RFC 2818 compliance; default SSL hostname verifier and default cookie policy now
- validate certificate identity and cookie domain of origin against the public suffix list
- maintained by Mozilla.org; native windows Negotiate/NTLM via JNA; more efficient stale
- connection checking; authentication cache thread-safety
-
-* 22 September 2014 - HttpComponents HttpCore 4.4-beta1 released
-
- This is the first BETA release from the 4.4.x development branch. The most notable features
- included in 4.4 series are: support for pipelined request processing on the server side;
- support for pipelined request execution on the client side; simplified bootstrapping of
- blocking and non-blocking (NIO) HTTP server implementations.
-
-* 10 Aug 2014 - HttpComponents HttpAsyncClient 4.0.2 (GA) released
-
- HttpAsyncClient 4.0.2 (GA) is a bug fix release that addresses several issues reported since
- release 4.0.1.
-
-* 10 Aug 2014 - HttpComponents HttpClient 4.3.5 (GA) released
-
- HttpClient 4.3.5 (GA) is a bug fix release that addresses several issues reported since
- release 4.3.4.
-
-* 30 June 2014 - HttpComponents HttpClient 4.4-alpha1 released
-
- This is the first ALPHA release from the 4.4.x development branch. Notable features and
- enhancements included this release are: more efficient stale connection checking, native
- Windows Negotiate/NTLM via JNA, authentication cache thread-safety
-
-* 18 June 2014 - HttpComponents HttpCore 4.4-alpha1 released
-
- This is the first release from the 4.4.x development branch. The most notable features included
- in this release are: support for pipelined request processing on the server side, support
- for pipelined request execution on the client sides, simplified bootstrapping of blocking and
- non-blocking (NIO) HTTP server implementations
-
-* 6 June 2014 - HttpComponents HttpClient 4.3.4 (GA) released
-
- HttpClient 4.3.4 (GA) is a maintenance release that improves performance in high concurrency
- scenarios. This version replaces dynamic proxies with custom proxy classes and eliminates
- thread contention in java.reflect.Proxy.newInstance() when leasing connections from
- the connection pool and processing response messages
-
-* 26 February 2014 - HttpComponents HttpClient 4.3.3 (GA) released
-
- HttpClient 4.3.3 (GA) is a bug fix release that fixes a regression introduced by the previous
- release causing a significant performance degradation in compressed content processing.
-
- Users of HttpClient 4.3 are encouraged to upgrade.
-
-* 24 February 2014 - HttpComponents HttpAsyncClient 4.0.1 (GA) released
-
- This maintenance release fixes a number of bugs including incorrect OSGi bundle metadata
- found since release 4.0. This release also upgrades HttpCore and HttpClient dependencies to
- the latest stable versions.
-
- Users of HttpAsyncClient 4.0 are advised to upgrade.
-
-* 17 February 2014 - HttpComponents HttpCore 4.3.2 (GA) released
-
- This maintenance release fixes a number of bugs and regressions found since 4.3.1, mostly
- in the NIO transport components. All users of HttpCore 4.3 are advised to upgrade.
-
-* 19 January 2014 - HttpComponents HttpClient 4.3.2 (GA) released
-
- HttpClient 4.3.2 (GA) is a maintenance release that delivers a number of improvements
- as well as bug fixes for issues reported since 4.3.1 release. SNI support for
- Oracle JRE 1.7+ is being among the most notable improvements.
-
- Users of HttpClient 4.3 are encouraged to upgrade.
-
-* 27 December 2013 - HttpComponents HttpCore 4.3.1 (GA) released
-
- This maintenance release fixes a number of bugs and regressions found since 4.3, mostly in the
- NIO transport components. All users of HttpCore 4.3 are advised to upgrade.
-
-* 31 October 2013 - HttpComponents HttpAsyncClient 4.0 (GA) released
-
- This is the first stable (GA) release of Apache HttpAsyncClient 4.0. HttpAsyncClient is
- a library for asynchronous client-side HTTP communication built on top of HttpCore NIO
- transport. It is a complementary library to Apache HttpClient intended and optimized for
- special cases whereby ability to scale to many thousands of concurrent connections is more
- important than performance in terms of raw data throughput.
-
- HttpAsyncClient 4.0 is designed to have similar APIs as Apache HttpClient 4.3 and a comparable
- feature set. In addition HttpAsyncClient provides full support for zero-copy file upload and
- download operations. It presently does not support transparent content decompression and
- automatic I/O error recovery. These features may be added in future releases.
-
-* 7 October 2013 - HttpComponents HttpClient 4.3.1 (GA) released
-
- This is a maintenance release that addresses a number of issues reported since release 4.3,
- including one major security issue. Users of HttpClient 4.3 are strongly advised to upgrade.
-
-* 12 September 2013 - HttpComponents HttpClient 4.3 (GA) released
-
- This is the first stable (GA) release of HttpClient 4.3. The 4.3 branch enhances HttpClient
- in several key areas and includes several notable features and improvements:
-
- * Support for Java 7 try-with-resources for resource management (connection release.)
-
- * Added fluent Builder classes for HttpEntity, HttpRequest, HttpClient and SSLContext instances.
-
- * Deprecation of preference and configuration API based on HttpParams interface in favor of
- constructor injection and plain configuration objects.
-
- * Reliance on object immutability instead of access synchronization for thread safety.
- Several old classes whose instances can be shared by multiple request exchanges have
- been replaced by immutable equivalents.
-
- * DefaultHttpClient, DecompressingHttpClient, CachingHttpClient and similar classes are
- deprecated in favor of builder classes that produce immutable HttpClient instances.
-
- * HttpClient builders now dynamically construct a request execution pipeline tailored
- specifically to the user configuration by physically excluding unnecessary protocol components.
-
- * There is now an option to construct a minimal HttpClient implementation that can only execute
- basic HTTP message exchanges without redirects, authentication, state management or proxy
- support. This feature might be of particular use in web crawler development.
-
- * There is now option to avoid strict URI syntax for request URIs by executing HTTP requests
- with an explicitly specified target host. HttpClient will no longer attempt to parse the request
- URI if it does not need to extract the target host from it.
-
- This release also includes all fixes from the stable 4.2.x release branch.
-
-* 12 September 2013 - HttpComponents HttpClient 4.2.6 (GA) released
-
- This is a maintenance release that addresses a number of non-critical issues reported
- since release 4.2.5.
-
-* 5 August 2013 - HttpComponents HttpCore 4.3 released
-
- This is the first stable (GA) release of HttpCore 4.3. The most notable features in the 4.3
- branch are:
-
- * Deprecation of preference and configuration API based on HttpParams interface in favor of
- constructor injection and plain configuration objects.
-
- * Reliance on object immutability instead of access synchronization for thread safety.
- Several old classes whose instances can be shared by multiple request exchanges have
- been replaced by immutable equivalents.
-
- []
-
- The 4.3 branch also contains performance optimizations such as reduced TCP packet
- fragmentation and more efficient lease / release operations for pools of persistent
- connections on the client side.
-
- This release also includes all fixes from the 4.2.x release branch.
-
-* 5 August 2013 - HttpComponents HttpCore 4.2.5 released
-
- This is a maintenance release that fixes a number of bugs found in NIO components since 4.2.4.
- Users of earlier versions of HttpCore 4.2 are advised to upgrade.
-
- This is likely to be the last release in the 4.2.x branch.
-
-* 12 June 2013 - HttpComponents HttpClient 4.3-beta2 released
-
- This is the second BETA release of HttpClient 4.3. The 4.3 branch enhances HttpClient in
- several key areas and includes several notable features and improvements: Support for Java 7
- try-with-resources for resource management (connection release); fluent Builder classes for
- HttpEntity, HttpRequest and HttpClient instances, deprecation of preference and configuration
- API based on HttpParams interface in favor of constructor injection and plain configuration
- objects, reliance on object immutability instead of access synchronization for thread safety.
-
- This release also includes all fixes from the stable 4.2.x release branch.
-
-* 16 May - HttpComponents HttpAsyncClient 4.0-beta4 released
-
- The 4.0 BETA4 release delivers significant performance improvements in request execution,
- especially for short HTTP messages, and also re-aligns programming interfaces used by
- the library with HttpCore 4.3 and HttpClient 4.3 APIs. Configuration and preference APIs of
- HttpAsyncClient are now consistent with those used by HttpClient 4.3.
-
-* 8 May - HttpComponents HttpCore 4.3-beta2 released
-
- This is the second BETA release from the 4.3.x release branch. This release addresses
- performance issues in the non-blocking connection pool implementation and also includes
- a number of performance improvements in the low level NIO based transport components.
-
-* 24 April 2013 - HttpComponents HttpClient 4.2.5 (GA) released
-
- This is a maintenance release that addresses a number of issues reported since release 4.2.4
- including a major bug that can lead to re-use of persistent connections in a inconsistent state.
-
-* 11 April 2013 - HttpComponents HttpClient 4.3-beta1 released
-
- This is the first BETA release of HttpClient 4.3. The 4.3 branch enhances HttpClient in
- several key areas and includes several notable features and improvements: Support for Java 7
- try-with-resources for resource management (connection release); fluent Builder classes for
- HttpEntity, HttpRequest and HttpClient instances, deprecation of preference and configuration
- API based on HttpParams interface in favor of constructor injection and plain configuration
- objects, reliance on object immutability instead of access synchronization for thread safety.
-
- This release also includes all fixes from the stable 4.2.x release branch.
-
-* 11 April 2013 - HttpComponents HttpClient 4.2.4 (GA) released
-
- This is a bug fix release that addresses a number of issues reported since release 4.2.3.
-
-* 25 March 2013 - HttpComponents HttpCore 4.3-beta1 released
-
- This is the first BETA release from the 4.3 release branch. The main theme of the 4.3 release
- series is streamlining of component configuration and deprecation of the old configuration
- API based on HttpParams in favor of constructor-based dependency injection and plain objects
- for configuration parameters.
-
- This release also includes performance optimizations intended to reduce TCP packet
- fragmentation when writing out HTTP messages both in blocking and non-blocking I/O modes,
- which should result in up to 20% higher throughput for short entity enclosing messages.
-
-* 25 March 2013 - HttpComponents HttpCore 4.2.4 released
-
- This is a maintenance release that fixes a number of bugs found in NIO components since 4.2.3.
- We advise users of HttpCore NIO of all versions to upgrade.
-
-* 21 January 2013 - HttpComponents HttpClient 4.3-alpha1 released
-
- This is the first ALPHA release of HttpClient 4.3. The 4.3 branch enhances HttpClient in
- several key areas and includes several notable features and improvements: Support for Java 7
- try-with-resources for resource management (connection release); fluent Builder classes for
- HttpEntity, HttpRequest and HttpClient instances, deprecation of preference and configuration
- API based on HttpParams interface in favor of constructor injection and plain configuration
- objects, reliance on object immutability instead of access synchronization for thread safety.
-
-* 15 January 2013 - HttpComponents HttpClient 4.2.3 (GA) released
-
- This is a bug fix release that addresses a number of issues reported since release 4.2.2.
- This release also includes a thoroughly reworked NTLM authentication engine which should
- result in a better compatibility with the newest Microsoft products.
-
-* 08 Dec 2012 - Welcome new HttpComponents committer Karl Wright
-
- Karl Wright has been unanimously voted in as a new HttpComponents committer due to his
- invaluable help in supporting the internal NTLM engine and NTLM related authentication code.
- Karl is a committer on a number of ASF projects: Lucene, Lucene connectors, Incubator.
-
- Welcome on board, Karl!
-
-* 30 November 2012 - HttpComponents HttpCore 4.3-alpha1 released
-
- This is the first release from the 4.3.x release branch. The main theme of the 4.3 release
- series is streamlining of component configuration and deprecation of the old configuration
- API based on HttpParams in favor of constructor-based dependency injection and plain objects
- for configuration parameters.
-
-* 30 November 2012 - HttpComponents HttpCore 4.2.3 (GA) released
-
- HttpCore 4.2.3 is a maintenance release that fixes a number of bugs found since 4.2.2
- including a major bug in the NIO module that can cause an infinite loop in SSL sessions
- under special circumstances when the remote peer terminates the session in the middle of
- SSL handshake. We advise users of HttpCore NIO of all versions to upgrade.
-
-* 25 October 2012 - HttpComponents HttpClient 4.2.2 (GA) released
-
- HttpClient 4.2.2 is a bug fix release that addresses a number of issues reported since
- release 4.2.1. Users of HttpClient 4.2 are advised to upgrade.
-
-* 29 September 2012 - HttpComponents HttpAsyncClient 4.0-beta3 released
-
- This is a maintenance release that picks up the latest bug fixes in the core components.
-
-* 23 September 2012 - HttpComponents HttpCore 4.2.2 (GA) released
-
- This is a maintenance release that fixes a number of bugs and regressions found since 4.2.1
- including a major bug in the NIO module causing incorrect handling of outgoing Content-Length
- delimited messages larger than 2GB. Users of HttpCore 4.2 are advised to upgrade.
-
-* 29 August 2012 - Welcome new HttpComponents committer William Speirs
-
- William Speirs, a long time contributor to the project, has been unanimously voted in as
- a new HttpComponents committer. William is already a committer on Apache Commons project.
-
- Welcome on board, William!
-
-* 8 August 2011 - HttpComponents HttpAsyncClient 4.0-beta2 released
-
- This release fixes a number of non-critical issues found since release 4.0-beta1 and
- introduces basic support for HTTP/1.1 response caching. Please note that caching for streaming
- HTTP exchanges is currently not supported.
-
-* 4 August 2012 - Welcome new HttpComponents committer Gary Gregory
-
- By 5 binding votes in favor Gary Gregory has been unanimously voted in as a new
- HttpComponents committer. Gary is already a committer on Apache Commons, Logging and Xalan
- projects.
-
- Welcome on board, Gary!
-
-* 5 July 2012 - HttpComponents HttpClient 4.2.1 (GA) released
-
- HttpClient 4.2.1 is a bug fix release that addresses a number of issues reported since
- release 4.2. Users of HttpClient 4.2 are advised to upgrade.
-
-* 14 June 2012 - HttpComponents HttpCore 4.2.1 (GA) released
-
- HttpCore 4.2.1 is a patch release that fixes a number of non-critical bugs found since 4.2.
- Users of HttpCore 4.2 are advised to upgrade.
-
-* 22 May 2012 - HttpComponents HttpClient 4.2 (GA) released
-
- This is the first stable (GA) release of HttpClient 4.2. The most notable enhancements included
- in this release are:
-
- * New facade API for HttpClient based on the concept of a fluent interface. The fluent API
- exposes only the most fundamental functions of HttpClient and is intended for relatively simple
- use cases that do not require the full flexibility of HttpClient. However, the fluent API
- almost fully relieves the users from having to deal with connection management and resource
- deallocation.
-
- * Redesigned and rewritten connection management code.
-
- * Enhanced HTTP authentication API that enables HttpClient to handle more complex
- authentication scenarios. HttpClient 4.2 is now capable of making use of multiple
- authentication challenges and retry authentication with a fall-back scheme in case the primary
- one fails. This can be important for compatibility with Microsoft products that are often
- configured to use SPNEGO/Kerberos as the preferred authentication scheme.
-
-* 5 May 2012 - HttpComponents HttpCore 4.2 (GA) released
-
- This is the first stable (GA) release of HttpCore 4.2. The most notable features included in
- this release are connection pool components for blocking and non-blocking HTTP connections and
- new asynchronous client and server side protocol handlers.
-
- New protocol handling API used in conjunction with connection pooling components is expected to
- make development of asynchronous HTTP client agents and HTTP proxies easier and less error
- prone.
-
- Connection pool components are based on mature code migrated from HttpClient and HttpAsyncClient
- modules but have a slightly different API that makes a better use of Java standard concurrent
- primitives.
-
-* 22 February 2012 - HttpComponents HttpAsyncClient 4.0-beta1 released
-
- This the first BETA release of HttpAsyncClient. This release completes the application
- programming interface and the feature set of HttpAsyncClient and upgrades to the latest
- versions of core and client components (HttpCore 4.2-beta1 and HttpClient 4.2-beta1).
- As of this release HttpAsyncClient is expected to be API stable.
-
-* 10 February 2012 - HttpComponents HttpClient 4.2-beta1 released
-
- This is the first BETA release of HttpClient 4.2. This release completes development of several
- notable enhancements in HttpClient: new facade API, redesigned connection management code
- and new HTTP authentication API.
-
-* 7 February 2012 - HttpComponents HttpClient 4.1.3 (GA) released
-
- HttpClient 4.1.3 is a bug fix release that addresses a number of non-critical issues found
- since 4.1.2 primarily in the HTTP caching module.
-
-* 1 February 2012 - HttpComponents HttpCore 4.2-beta1 released
-
- This is the first BETA release of HttpCore 4.2. This release ships with an improved
- asynchronous protocol handling API and new non-blocking client and server HTTP protocol handler
- implementations. New API is expected to be more flexible especially for writing HTTP proxy or
- gateway type of services. Upstream projects are encouraged to evaluate the new API and
- give feedback.
-
-* 23 December 2011 - HttpComponents HttpCore 4.1.4 (GA) released
-
- HttpCore 4.1.4 is a patch release that fixes a number of bugs found since 4.1.3. It is also
- likely to be the last release in the 4.1.x branch.
-
-* 3 November 2011 - HttpComponents HttpClient 4.2-alpha1 released
-
- This is the first ALPHA release of HttpClient 4.2. The 4.2 branch enhances HttpClient in several
- key areas and includes several notable features and improvements: new facade API, redesigned
- connection management code and new HTTP authentication API.
-
-* 29 September 2011 - HttpComponents HttpAsyncClient 4.0-alpha3 released
-
- This is the third ALPHA release of HttpAsyncClient 4.0. This release largely completes
- the application programming interface and feature set of HttpAsyncClient. While the API may
- still change in the course of the ALPHA development phase, this is expected to be the last
- round of major API changes and the API is expected to be reasonably stable as of this release.
-
-* 23 September 2011 - HttpComponents HttpCore 4.2-alpha2 released
-
- This is the second ALPHA release of HttpCore 4.2. This release comes with completely redesigned
- and rewritten asynchronous protocol handlers. New protocol handling API used in conjunction
- with connection pooling components introduced in the previous ALPHA release is expected to make
- development of asynchronous HTTP client agents and HTTP proxies easier and less error prone.
-
-* 19 August 2011 - HttpComponents HttpCore 4.2-alpha1 released
-
- This is the first ALPHA release of the 4.2 development branch. The most notable feature
- included in this release is support for connection pools of blocking and non-blocking HTTP
- connections. Connection pool components are based on mature code migrated from HttpClient and
- HttpAsyncClient modules but have a slightly different API that makes a better use of Java
- standard concurrent primitives. Support for connection pools in HttpCore is expected to make
- development of client and proxy HTTP services easier and less error prone.
-
-* 7 August 2011 - HttpComponents HttpClient 4.1.2 (GA) released
-
- HttpClient 4.1.2 is a bug fix release that addresses a number of non-critical issues reported
- since release 4.1.1.
-
-* 31 July 2011 - HttpComponents HttpCore 4.1.3 (GA) released
-
- HttpCore 4.1.3 is a patch release that fixes a critical regression in the non-blocking SSL I/O
- session code introduced in the 4.1.2 release.
-
-* 18 July 2011 - HttpComponents HttpCore 4.1.2 (GA) released
-
- HttpCore 4.1.2 is a patch release that fixes a number of non-critical issues found since
- release 4.1.1.
-
-* 24 May 2011 - HttpComponents HttpAsyncClient 4.0-alpha2 released
-
- The second ALPHA release of HttpAsyncClient 4.0 comes with a number of important improvements
- and enhancements. As of this version HttpAsyncClient fully supports HTTP state management
- (cookies) and HTTP authentication (basic, digest, NTLM, spnego/kerberos). Connection management
- classes have been thoroughly reworked and improved. This version also improves support for zero
- copy file upload / download operations.
-
-* 20 May 2011 - HttpComponents HttpCore 4.1.1 (GA) released
-
- HttpCore 4.1.1 is a patch release that fixes a number of non-critical issues found since
- release 4.1.
-
- This release marks the end of support for Java 1.3. As of release 4.2 HttpCore will require
- Java 1.5 for all its components.
-
-* 20 March 2011 - HttpComponents HttpClient 4.1.1 (GA) released
-
- HttpClient 4.1.1 is a bug fix release that addresses a number of issues reported since
- release 4.1, including one critical security issue.
-
-* 23 January 2011 - HttpComponents HttpClient 4.1 (GA) released
-
- The HttpClient 4.1 release builds upon the stable foundation laid by HttpClient 4.0 and adds
- several functional improvements and popular features.
-
- * Response caching conditionally compliant with HTTP/1.1 specification (full compliance with
- MUST requirements, partial compliance with SHOULD requirements)
-
- * Full support for NTLMv1, NTLMv2, and NTLM2 Session authentication. The NTLM protocol code
- was kindly contributed by the Lucene Connector Framework project.
-
- * Support for SPNEGO/Kerberos authentication.
-
- * Persistence of authentication data between request executions within the same execution context.
-
- * Support for preemptive authentication for BASIC and DIGEST schemes.
-
- * Support for transparent content encoding. Please note transparent content encoding is not
- enabled per default in order to avoid conflicts with already existing custom content encoding
- solutions.
-
- * Mechanism to bypass the standard certificate trust verification (useful when dealing with
- self-signed certificates).
-
- * Simplified configuration for connection managers.
-
- * Transparent support for host multihoming.
-
-* 18 January 2011 - HttpComponents HttpAsyncClient 4.0-alpha1 released
-
- This is the first public release of HttpAsyncClient. The HttpAsyncClient 4.0 API is considered
- very experimental and is expected to change in the course of the ALPHA development phase. This
- release is primarily intended for early adopters who may be interested in contributing to
- the project and in helping shape the new API.
-
-* 21 November 2010 - HttpComponents HttpClient 4.1-beta1 released
-
- This release finalizes the 4.1 API and brings a number of major improvements to the HTTP
- caching module. This release also adds full support for NTLMv1, NTLMv2, and NTLM2 Session
- authentication schemes. The NTLM protocol code was kindly contributed by the Lucene Connector
- Framework project.
-
-* 19 November 2010 - HttpComponents HttpCore 4.1 (GA) released
-
- This is the first stable release of HttpCore 4.1. This release provides a compatibility mode
- with JREs that have a naive (broken) implementation of SelectionKey API and also improves
- compatibility with the Google Android platform. There has also been a number of performance
- related improvements and bug fixes in both blocking and non-blocking components.
-
-* 26 October 2010 - Welcome new HttpComponents committer Jonathan Moore
-
- By 4 binding votes in favor and none against Jonathan Moore has been voted in as a new
- HttpComponents committer. Jonathan has made major contributions to the new HttpClient caching
- module.
-
- Welcome on board, Jonathan!
-
-* 19 September 2010 - HttpComponents HttpClient 4.0.3 (GA) released
-
- This is an emergency release fixing a critical regression in the SSL
- connection management code.
-
-* 9 September 2010 - HttpComponents HttpClient 4.0.2 (GA) released
-
- This is a maintenance release that fixes a number of bugs found since 4.0.1.
- This is likely to be the last release in the 4.0.x branch.
-
-* 30 August 2010 - HttpComponents HttpCore 4.1-beta2 released
-
- This release addresses fixes a number of non-critical bugs. It is likely to be
- the last BETA release in the 4.1 branch.
-
-* 19 May 2010 - HttpComponents HttpClient 4.1-alpha2 released
-
- This release fixes a number of non-severe bugs discovered since the last release
- and introduces support for two frequently requested features:
-
- * HTTP/1.1 response caching
-
- * transparent support for host multihoming
-
- * a mechanism to bypass the standard certificate trust verification (useful when
- dealing with self-signed certificates)
-
-* 3 April 2010 - HttpComponents HttpCore 4.1-beta1 released
-
- This release finalizes the API introduced in the 4.1 development branch. It also
- fixes a number of bugs discovered since the previous release and delivers a number
- of performance optimizations in the blocking HTTP transport components. The blocking
- HTTP transport is expected to be 5% to 10% faster compared to previous releases.
-
-* 11 December 2009 - HttpComponents HttpClient 4.1-alpha1 released
-
- This release builds on the stable 4.0 release and adds several functionality
- improvements and new features.
-
- * Simplified configuration of connection managers.
-
- * Persistence of authentication data between request executions within
- the same execution context.
-
- * Support for SPNEGO/Kerberos authentication scheme
-
- * Support for transparent content encoding. Please note transparent content
- encoding is not enabled per default in order to avoid conflicts with
- already existing custom content encoding solutions.
-
-* 11 December 2009 - HttpComponents HttpClient 4.0.1 (GA) released
-
- This is a bug fix release that addresses a number of issues discovered since
- the previous stable release. None of the fixed bugs is considered critical.
- Most notably this release eliminates dependency on JCIP annotations.
-
- This release is also expected to improve performance by 5 to 10% due to
- elimination of unnecessary Log object lookups by short-lived components.
-
-* 12 September 2009 - HttpComponents HttpCore 4.1-alpha1 released
-
- This is the first public release from the 4.1 branch of HttpCore. This release
- adds a number of new features, most notable being introduction of compatibility
- mode with IBM JREs and other JREs with naive (broken) implementation
- of SelectionKey API.
-
-* 14 August 2009 - HttpComponents HttpClient 4.0 (GA) released
-
- This the first stable (GA) release in the 4.x code line. This release completes
- the rewrite of HttpClient and delivers a complete API documentation and fixes
- a few minor bugs reported since the previous release.
-
-* 22 June 2009 - HttpComponents HttpCore 4.0.1 (GA) released
-
- This is a patch release addressing a number of issues discovered since the 4.0
- release.
-
-* 26 February 2009 - HttpComponents HttpCore 4.0 (GA) released
-
- This the first stable (GA) release in the 4.x code line. This release delivers
- complete API documentation and fixes a few minor bugs reported since
- the previous release.
-
-* 20 December 2008 - HttpComponents HttpClient 4.0-beta2 released
-
- The second BETA of HttpComponents HttpClient addresses a number of issues
- discovered since the previous release.
-
- The only significant new feature is an addition of an OSGi compliant bundle
- combining HttpClient and HttpMime jars.
-
- All upstream projects are strongly encouraged to upgrade.
-
-* 19 October 2008 - HttpComponents HttpCore 4.0-beta3 released
-
- The third BETA version of HttpComponents Core addresses a number of issues
- discovered since the previous release.
-
- The only significant new feature is an addition of an OSGi compliant bundle
- combining HttpCore and HttpCore NIO jars.
-
-* 12 September 2008 - HttpClient is one of the best open source development tools
-
- HttpClient is among the 60 winners of InfoWorlds
- {{{http://www.infoworld.com/article/08/08/04/32TC-bossies-2008_1.html}
- "Best of Open Source Software Awards 2008"}}.
-
- HttpClient was selected as one of the
- {{{http://www.infoworld.com/slideshow/2008/08/166-best_of_open_so-4.html}
- best open source development tools}}.
-
-* 29 August 2008 - HttpComponents HttpClient 4.0-beta1 released
-
- The first BETA brings yet another round of API enhancements and
- improvements in the area of connection management. Among the most notable
- ones is the capability to handle stateful connections such as persistent
- NTLM connections and private key authenticated SSL connections.
-
- This is the first API stable release of HttpClient 4.0. All further
- releases in the 4.0 code line will maintain API compatibility with this
- release.
-
-* 22 June 2008 - HttpComponents HttpCore 4.0-beta2 released
-
- The second BETA version of HttpComponents Core added a number of improvements
- to the NIO components, most notable being improved asynchronous client side and
- server side protocol handlers.
-
-* 09 May 2008 - HttpComponents HttpClient 4.0-alpha4 released
-
- The fourth ALPHA marks the completion of the overhaul of the connection
- management code in HttpClient. All known shortcomings of the old HttpClient
- 3.x connection management API have been addressed.
-
-* 03 May 2008 - Welcome new HttpComponents committer Sam Berlin
-
- By 6 binding votes in favor and none against Sam Berlin has been voted in as a new
- HttpComponents committer. Sam made several valuable contributions to both core
- and client components in the course of the past several months.
-
- Welcome on board, Sam!
-
-* 26 February 2008 - HttpComponents HttpClient 4.0-alpha3 released
-
- The third ALPHA release brings another round of API refinements and improvements
- in functionality. As of this release HttpClient requires Java 5 compatible
- runtime environment and takes full advantage of generics and new concurrency
- primitives.
-
- This release also introduces new default cookie policy that selects a cookie
- specification depending on the format of cookies sent by the target host.
- It is no longer necessary to know beforehand what kind of HTTP cookie support
- the target host provides. HttpClient is now able to pick up either a lenient
- or a strict cookie policy depending on the compliance level of the target host.
-
- Another notable improvement is a completely reworked support for multipart
- entities based on Apache mime4j library.
-
-* 24 January 2008 - HttpComponents HttpCore 4.0-beta1 released
-
- The first BETA version of HttpComponents Core has been released. This release
- can be considered a major milestone, as it marks the end of API instability
- in HttpCore. As of this release the API compatibility between minor releases
- in 4.x codeline will be maintained.
-
- This release includes several major improvements such as enhanced HTTP message
- parsing API and optimized parser implementations, Java 5.0 compatibility
- for HttpCore NIO extensions.
-
- The focus of the development efforts will be gradually shifting towards
- providing better test coverage, documentation and performance optimizations.
-
-* 15 November 2007 - HttpComponents becomes TLP
-
- The ASF board had approved HttpComponents 'graduation' from Jakarta to a TLP of its own.
-
- We are now Apache HttpComponents Project!
-
-* 7 November 2007 - HttpComponents HttpClient 4.0-alpha2 released
-
- The second ALPHA release is another important milestone in the redesign of HttpClient. The
- release includes a number of improvements since ALPHA1, among which are improved connection
- pooling, support for proxy chains, redesigned HTTP state and authentication credentials
- management API, improved RFC 2965 cookie specification.
-
-* 9 October 2007 - HttpComponents HttpCore 4.0-alpha6 released
-
- The sixth ALPHA version of HttpComponents Core has been released. This release sports an
- improved message parsing and formatting API in the base module and lots of incremental
- improvements and bug fixes in the NIO and NIOSSL modules. Based on the improved API, it is now
- possible to send and receive SIP messages with HttpComponents Core.
-
-* 20 July 2007 - HttpComponents HttpClient 4.0-alpha1 released
-
- This release represents a complete, ground-up redesign and almost a complete rewrite of the old
- HttpClient 3.x codeline. This release finally addresses several design flaws that existed since
- the 1.0 release and could not be fixed without a major code overhaul and breaking API
- compatibility.
-
- Notable changes and enhancements:
-
- * Redesign of the HttpClient internals addressing all known major architectural shortcomings of
- the 3.x codeline
-
- * Cleaner, more flexible and expressive API
-
- * Better performance and smaller memory footprint due to a more efficient HTTP transport based
- on HttpCore. HttpClient 4.0 is expected to be 10% to 25% faster than HttpClient 3.x codeline
-
- * More modular structure
-
- * Pluggable redirect and authentication handlers
-
- * Support for protocol incerceptors
-
- * Improved connection management
-
- * Improved support for sending requests via a proxy or a chain of proxies
-
- * Improved handling redirects of entity enclosing requests
-
- * More flexible SSL context customization
-
- * Reduced intermediate garbage in the process of generating HTTP requests and parsing HTTP
- responses
-
-* 4 July 2007 - HttpComponents HttpCore 4.0-alpha5 released
-
- The fifth ALPHA version of HttpComponents Core has been released. This release delivers a number
- of incremental improvements across the board in all modules and adds several performance oriented
- features such as ability to transfer data directly between a file and a socket NIO channels.
-
-* 30 March 2007 - HttpComponents HttpCore 4.0-alpha4 released
-
- The fourth ALPHA version fixes a number of bugs and adds a number of improvements to HttpCore
- base and the HttpCore NIO extensions. This release also introduces NIOSSL extensions that can be
- used to extend HttpCore non-blocking transport components with the ability to transparently encrypt
- data in transit using SSL/TLS.
-
-* 6 December 2006 - HttpComponents HttpCore 4.0-alpha3 released
-
- The third ALPHA version of HttpCore has been released. The ALPHA3 release includes a number of API
- optimizations and improvements and introduces a set of NIO extensions to the HttpCore API.
- NIO extensions can be used to build HTTP services intended to handle thousands of simultaneous
- connections with a small number of I/O threads.
-
-* 9 June 2006 - HttpComponents HttpCore 4.0-alpha2 released
-
- The second ALPHA version of HttpCore has been released, which addresses a number of non-critical
- problems found in the previous release. The upstream projects are strongly encouraged use this
- release as a dependency while HttpCore undergoes another round of reviews and optimization in the
- SVN trunk.
-
-* 12 May 2006 - HttpClient issue tracking migrated to Jira
-
- HttpClient issue tracking has migrated from Bugzilla to Jira. Please use
- {{{http://issues.apache.org/jira/browse/HTTPCLIENT}this project}} in Jira
- to report new issues against HttpClient and search for reported ones. All existing
- issue reports can be accessed in Jira by their original Bugzilla bug id.
-
-* 29 April 2006 - New Project Logo
-
- HttpComponents project now has a brand new logo kindly contributed by Regula Wernli.
-
- Many thanks, Regula!
-
-* 23 April 2006 - HttpComponents HttpCore 4.0-alpha1 released
-
- This is the first ALPHA release of HttpCore intended for API review and use in
- experimental projects. The HttpCore API is still deemed unstable and it can still
- undergo significant changes based on the feedback from early adopters.
-
-* 12 February 2006 - Welcome new HttpComponents committer Roland Weber
-
- By 5 binding votes in favor and none against Roland Weber has been voted in as a new
- HttpComponents committer. Roland has been an invaluable contributor to the Jakarta
- Commons HttpClient project for many years and he is the very first committer to
- join the Jakarta HttpComponents project.
-
- Welcome, Roland
-
-* 31 October 2005 - Jakarta HttpClient becomes Jakarta HttpComponents
-
- By the count 15 votes in favor, Jakarta HttpClient as been renamed as Jakarta HttpComponents.
- The Jakarta PMC has approved the new project charter and the new project scope.
-
-* 16 April 2004 - Welcome Jakarta HttpClient!
-
- By the count 26 votes in favor, none against, Jakarta Commons HttpClient as been promoted to
- the Jakarta sub-project level
diff --git a/src/site/apt/poweredby.apt b/src/site/apt/poweredby.apt
deleted file mode 100644
index c68412f..0000000
--- a/src/site/apt/poweredby.apt
+++ /dev/null
@@ -1,88 +0,0 @@
-~~ ====================================================================
-~~ Licensed to the Apache Software Foundation (ASF) under one
-~~ or more contributor license agreements. See the NOTICE file
-~~ distributed with this work for additional information
-~~ regarding copyright ownership. The ASF licenses this file
-~~ to you under the Apache License, Version 2.0 (the
-~~ "License"); you may not use this file except in compliance
-~~ with the License. You may obtain a copy of the License at
-~~
-~~ http://www.apache.org/licenses/LICENSE-2.0
-~~
-~~ Unless required by applicable law or agreed to in writing,
-~~ software distributed under the License is distributed on an
-~~ "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
-~~ KIND, either express or implied. See the License for the
-~~ specific language governing permissions and limitations
-~~ under the License.
-~~ ====================================================================
-~~
-~~ This software consists of voluntary contributions made by many
-~~ individuals on behalf of the Apache Software Foundation. For more
-~~ information on the Apache Software Foundation, please see
-~~ <http://www.apache.org/>.
-
- -----------
- Powered by HttpComponents
-
-Powered by HttpComponents
-
-* Apache Synapse
-
- {{{http://ws.apache.org/synapse/}Apache Synapse}} uses HttpComponents
- HttpCore to provide completely non-blocking HTTP support as an ESB and
- XML Gateway. The Synapse development team has done a number of
- performance tests including loading up more than 2000 concurrent clients,
- resulting in 4000 concurrent HTTP connections in and out of Synapse -
- all with a fixed small thread pool and no loss of data. Paul Fremantle,
- chair of the Apache Synapse PMC said: "HttpCore is a key part of Apache
- Synapse - and absolutely essential to our high-performance HTTP support.
- The HttpComponents team have always been extremely helpful and the
- quality of the code speaks for itself".
-
-* jfireeagle
-
- {{{http://code.google.com/p/jfireeagle} jfireeagle}} is a Java client library for Yahoo {{{http://fireeagle.yahoo.net} Fire Eagle}}
-
-* jtrimet
-
- {{{http://code.google.com/p/jtrimet} jtrimet}} is a Java client library for {{{http://developer.trimet.org/ws_docs}TriMet's web service}}
-
-* jpoco
-
- {{{http://code.google.com/p/jpoco} jpoco}} is a Java client library for {{{http://portablecontacts.net} PortableContacts}}
-
-* JClouds
-
- {{{http://code.google.com/p/jclouds/}JClouds}} provides concurrent apis to
- popular cloud services. HttpCore NIO powers JClouds' server-grade
- {{{http://aws.amazon.com/s3/}S3}} connector, allowing non-blocking uploads of
- String, InputStream, File, and byte [] data without expensive conversions.
-
-* AdroitLogic UltraESB
-
- The {{{https://www.adroitlogic.com/products/ultraesb/}AdroitLogic UltraESB}} uses HttpCore and HttpCore NIO
- extensions, as well as the HttpClient, to build a high performance, feature rich, easy
- to use and lightweight Enterprise Service Bus (ESB). UltraESB is the first ESB to offer Zero-Copy
- proxying coupled with NIO, to offer extreme levels of
- {{{http://esbperformance.org} ESB performance}}. Apache HttpComponents is a key
- component of the UltraESB and the {{{https://www.adroitlogic.com/products/ips/}AdroitLogic Integration Platform}} offering a container-based integration solution for
- private, public and hybrid cloud deployments.
-
-* Apache ManifoldCF
-
- The {{{http://manifoldcf.apache.org}Apache ManifoldCF}} project uses HttpCore
- and HttpClient for many of its repository and output connectors. These are connectors
- to repositories like Microsoft SharePoint and OpenText LiveLink, as well as output
- connectors for Elastic Search and Open Search Server. ManifoldCF also uses HttpComponents
- libraries for crawling the open web.
-
-* ESIGate
-
- {{{http://www.esigate.org/}ESIGate}} is a reverse-proxy that fully implements the
- {{{http://www.w3.org/TR/esi-lang}ESI Language Specification}} allowing to build a website
- as a mashup of several websites, applications or tools like content management systems.
- Thanks to HttpClient's caching system, ESIGate also acts as a powerfull web accelerator
- and powers major websites. ESIGate can be deployed standalone or as a web application in
- any java Servlet container.
-
diff --git a/src/site/apt/status.apt b/src/site/apt/status.apt
deleted file mode 100644
index 53fb9db..0000000
--- a/src/site/apt/status.apt
+++ /dev/null
@@ -1,84 +0,0 @@
-~~ ====================================================================
-~~ Licensed to the Apache Software Foundation (ASF) under one
-~~ or more contributor license agreements. See the NOTICE file
-~~ distributed with this work for additional information
-~~ regarding copyright ownership. The ASF licenses this file
-~~ to you under the Apache License, Version 2.0 (the
-~~ "License"); you may not use this file except in compliance
-~~ with the License. You may obtain a copy of the License at
-~~
-~~ http://www.apache.org/licenses/LICENSE-2.0
-~~
-~~ Unless required by applicable law or agreed to in writing,
-~~ software distributed under the License is distributed on an
-~~ "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
-~~ KIND, either express or implied. See the License for the
-~~ specific language governing permissions and limitations
-~~ under the License.
-~~ ====================================================================
-~~
-~~ This software consists of voluntary contributions made by many
-~~ individuals on behalf of the Apache Software Foundation. For more
-~~ information on the Apache Software Foundation, please see
-~~ <http://www.apache.org/>.
-
- ----------
- HttpComponents Status
- ----------
- ----------
- ----------
-
-HttpComponents Project Status
-
-* {HttpComponents HttpCore 5.1.x}
-
- HttpCore 5.1.x branch is the current feature development branch. The 5.x release
- series is expected to provide conditional conformance to RFC 3986 as well as
- a number of incremental functional enhancements and performance improvements.
-
-* {HttpComponents HttpCore 5.0.x}
-
- HttpCore 5.0.x branch is considered stable and production ready. It is being actively
- maintained and supported. The 5.x release series provides comprehensive support
- for HTTP/1.1 and HTTP/2 protocol and full conformance with mandatory requirements
- of RFC 7230, RFC 7231, RFC 7540 and RFC 7541
-
- Users of all versions of HttpCore are advised to upgrade to the latest release
- of the 5.0 series.
-
-* {HttpComponents HttpClient 5.0.x}
-
- HttpClient 5.0.x branch is considered stable and production ready. It is being actively
- maintained and supported. The 5.x release series provides comprehensive support
- for HTTP/1.1 and HTTP/2 protocol and full conformance with mandatory requirements
- of RFC 7230, RFC 7231, RFC 7540 and RFC 7541
-
- Users of all versions of HttpClient are advised to upgrade to the latest release
- of the 5.0 series.
-
-* {HttpComponents HttpCore 4.4.x}
-
- HttpCore 4.4.x branch is considered stable and production ready. While being actively
- maintained and supported, the 4.x release series will be receiving fixes for major defects
- and security issues only.
-
-* {HttpComponents HttpClient 4.5.x}
-
- HttpClient 4.5.x branch is considered stable and production ready. While being actively
- maintained and supported, the 4.x release series will be receiving fixes for major defects
- and security issues only.
-
-* {HttpComponents HttpAsyncClient 4.1.x}
-
- HttpAsyncClient 4.1.x branch is considered stable and production ready. While being actively
- maintained and supported, the 4.x release series will be receiving fixes for major defects
- and security issues only.
-
-* {Commons HttpClient 3.1.x}
-
- The 3.1 branch of Commons HttpClient is at the end of life. No more public releases are
- expected.
-
-
-
-
diff --git a/src/site/markdown/charter.md b/src/site/markdown/charter.md
new file mode 100644
index 0000000..f728bbd
--- /dev/null
+++ b/src/site/markdown/charter.md
@@ -0,0 +1,134 @@
+<!--
+ Licensed to the Apache Software Foundation (ASF) under one
+ or more contributor license agreements. See the NOTICE file
+ distributed with this work for additional information
+ regarding copyright ownership. The ASF licenses this file
+ to you under the Apache License, Version 2.0 (the
+ "License"); you may not use this file except in compliance
+ with the License. You may obtain a copy of the License at
+
+ http://www.apache.org/licenses/LICENSE-2.0
+
+ Unless required by applicable law or agreed to in writing,
+ software distributed under the License is distributed on an
+ "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+ KIND, either express or implied. See the License for the
+ specific language governing permissions and limitations
+ under the License.
+-->
+
+<!--
+ The Charter was approved by a PMC vote ending on 2008-02-09.
+ Changes to the Charter require PMC approval.
+ DO NOT EDIT the "Charter" section, not even to fix typos.
+-->
+
+Charter
+-------
+
+The Apache HttpComponents project is responsible for creating and maintaining a toolset of low level Java components
+focused on HTTP and associated protocols.
+
+We develop and maintain a component called `HttpCore`, which addresses the basic needs for communicating via HTTP on the
+client and server side. HttpCore defines a framework for extending the provided functionality beyond the basic needs.
+
+We develop and maintain a component called `HttpClient`, which builds on HttpCore and adds functionality typically
+required for client-side HTTP communication. In particular, HttpClient adds support for cookies, authentication, and
+client-side connection management.
+
+`HttpCore` and `HttpClient` are at the center of the Apache HttpComponents project. All other activities orbit around
+this duo.
+
+We maintain the codebase of the Jakarta Commons HttpClient, also known as Commons HttpClient 3.1, until such time that
+the new HttpClient based on HttpCore is considered ready for use in production systems.
+
+We are looking for new components that build upon and extend the functionality of the existing ones. We are also looking
+for new components that complement the functionality of the existing ones and make them more useful or easier to use.
+
+We are open to give a home to applications that derive a significant part of their functionality from our components, if
+approached by such projects.
+
+<!--
+end of the "Charter" section that must not be edited without PMC approval
+-->
+
+History
+-------
+
+The history of the HttpComponents starts with the now retired
+[Jakarta Slide](http://jakarta.apache.org/slide/) project. Slide was a WebDAV server including a client component, and
+the WebDAV protocol builds on HTTP. There was interest in using the client-side HTTP implementation independently of
+Slide. The code was spun off from Slide in 2001 to become the HttpClient subproject of the Jakarta Commons.
+
+Since it generated a disproportional amount of traffic on the Commons mailing lists, HttpClient activity was moved to
+separate mailing lists. This started the dissociation of HttpClient from Commons, which continued when HttpClient was
+promoted to the Jakarta subproject level in 2004. The latter event is recorded as the oldest [News](news.md) item of the
+HttpComponents project.
+
+The [Commons](http://commons.apache.org/), cradle of HttpClient, left Jakarta in 2007 to become an independent Top Level
+Project. Later in the same year, the HttpComponents project also left Jakarta to become an independent Top Level
+Project, taking the responsibility for maintaining HttpClient 3.x with it. Our TLP resolution is presented below.
+
+Resolution
+----------
+
+The Apache HttpComponents project was established as an Apache top level project in November 2007, when the Apache Board
+approved the following resolution:
+
+<!--
+The following is a verbatim copy of the TLP resolution.
+DO NOT EDIT, not even to fix typos
+-->
+
+---------
+```text
+Establish the Apache HttpComponents project
+
+WHEREAS, the Board of Directors deems it to be in the best interests of the Foundation and
+consistent with the Foundation\'s purpose to establish a Project Management Committee charged with
+the creation and maintenance of open-source software related to a toolset of low level Java
+components focused on HTTP and associated protocols, and of applications based on these components,
+for distribution at no charge to the public.
+
+NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee (PMC), to be known as "Apache
+HttpComponents Project", be and hereby is established pursuant to Bylaws of the Foundation; and be
+it further
+
+RESOLVED, that the Apache HttpComponents Project be and hereby is responsible for the creation and
+maintenance of a toolset of low level Java components focused on HTTP and associated protocols, and
+of applications based on these components; and be it further
+
+RESOLVED, that the office of "Vice President, Apache HttpComponents" be and hereby is created, the
+person holding such office to serve at the direction of the Board of Directors as the chair of the
+Apache HttpComponents Project, and to have primary responsibility for management of the projects
+within the scope of responsibility of the Apache HttpComponents Project; and be it further
+
+RESOLVED, that the persons listed immediately below be and hereby are appointed to serve as the
+initial members of the Apache HttpComponents Project:
+
+ * Oleg Kalnichevski <olegk AT apache DOT org>
+ * Sebastian Bazley <sebb AT apache DOT org>
+ * Erik Abele <erikabele AT apache DOT org>
+ * Ortwin Gl�ck <oglueck AT apache DOT org>
+ * Roland Weber <rolandw AT apache DOT org>
+ * Ant Elder <antelder AT apache DOT org>
+ * Paul Fremantle <pzf AT apache DOT org>
+ * Asankha Perera <asankha AT apache DOT org>
+
+NOW, THEREFORE, BE IT FURTHER RESOLVED, that Erik Abele be appointed to the office of Vice
+President, Apache HttpComponents, to serve in accordance with and subject to the direction of the
+Board of Directors and the Bylaws of the Foundation until death, resignation, retirement, removal or
+disqualification, or until a successor is appointed; and be it further
+
+RESOLVED, that the Apache HttpComponents Project be and hereby is tasked with the migration and
+rationalization of the Apache Jakarta HttpComponents subproject; and be it further
+
+RESOLVED, that the Apache HttpComponents Project be and hereby is tasked with the migration and
+maintenance of the codebase formerly known as Apache Jakarta Commons HttpClient until it is
+obsoleted by the components of the Apache HttpComponents Project; and be it further
+
+RESOLVED, that all responsibilities pertaining to the Apache Jakarta HttpComponents subproject and
+the former Apache Jakarta Commons HttpClient codebase encumbered upon the Apache Jakarta Project are
+hereafter discharged.
+```
+--------
diff --git a/src/site/markdown/get-involved.md b/src/site/markdown/get-involved.md
new file mode 100644
index 0000000..cbaf22e
--- /dev/null
+++ b/src/site/markdown/get-involved.md
@@ -0,0 +1,65 @@
+<!--
+ Licensed to the Apache Software Foundation (ASF) under one
+ or more contributor license agreements. See the NOTICE file
+ distributed with this work for additional information
+ regarding copyright ownership. The ASF licenses this file
+ to you under the Apache License, Version 2.0 (the
+ "License"); you may not use this file except in compliance
+ with the License. You may obtain a copy of the License at
+
+ http://www.apache.org/licenses/LICENSE-2.0
+
+ Unless required by applicable law or agreed to in writing,
+ software distributed under the License is distributed on an
+ "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+ KIND, either express or implied. See the License for the
+ specific language governing permissions and limitations
+ under the License.
+-->
+
+Get Involved With HttpComponents
+================================
+
+Community
+---------
+
+- Users mailing list: [httpclient-users@](mailto:httpclient-users@hc.apache.org) for general discussion, questions, and
+ announcements. This is the perfect place to ask for help if you need it!
+- Development mailing list: [dev@](mailto:dev@hc.apache.org) for discussion about project development.
+- GitHub: Star us at [apache/httpcomponents-core](https://github.com/apache/httpcomponents-core/)
+ and [apache/httpcomponents-client](https://github.com/apache/httpcomponents-client/) and use this to follow
+ HttpComponents development or contribute pull requests. If you're interested in development, please see the
+ Contributing section below for details on our development process.
+- Reporting issues:
+
+ - [HttpComponents Core](https://issues.apache.org/jira/projects/HTTPCORE)
+ - [HttpComponents Client](https://issues.apache.org/jira/projects/HTTPCLIENT)
+
+- Slack: Some committers and users are present in the
+ channel [#httpcomponents-client](https://the-asf.slack.com/archives/CGC9KPJKH) on the Apache Slack team.
+- StackOverflow: While the user mailing list is the primary resource for asking questions, if you prefer StackOverflow,
+ make sure to tag your question
+ with [apache-httpcomponents](https://stackoverflow.com/questions/tagged/apache-httpcomponents).
+
+Contributing
+------------
+
+HttpComponents is a community-led project, and we are delighted to receive contributions of anything from minor fixes to
+new features. If you have an itch to scratch, then by all means do that! Fixing bugs you run into, or adding features
+you need, are both immensely helpful. There are plenty of ways to help outside writing code. Code review of pull
+requests (even if you are not a committer), feature suggestions, reporting bugs, documentation and usability feedback
+all matter immensely.
+
+Testing
+-------
+
+All Pull Requests are automatically tested on [Travis CI (Core)](https://travis-ci.com/apache/httpcomponents-core)
+, [Travis CI (Client)](https://travis-ci.com/apache/httpcomponents-client) on both AMD64 and ARM64 architectures.
+
+More information
+----------------
+
+As it happens, the ways to get involved into an open source project are basically the same for all projects. Please have
+a look at the [Incubator Guide To Participation](http://incubator.apache.org/guides/participation.html). It's terse, but
+has pointers to additional information elsewhere at Apache. The sections on participating as a User and as a Developer
+apply here, too.
diff --git a/src/site/markdown/index.md b/src/site/markdown/index.md
new file mode 100644
index 0000000..d721bff
--- /dev/null
+++ b/src/site/markdown/index.md
@@ -0,0 +1,60 @@
+<!--
+ Licensed to the Apache Software Foundation (ASF) under one
+ or more contributor license agreements. See the NOTICE file
+ distributed with this work for additional information
+ regarding copyright ownership. The ASF licenses this file
+ to you under the Apache License, Version 2.0 (the
+ "License"); you may not use this file except in compliance
+ with the License. You may obtain a copy of the License at
+
+ http://www.apache.org/licenses/LICENSE-2.0
+
+ Unless required by applicable law or agreed to in writing,
+ software distributed under the License is distributed on an
+ "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+ KIND, either express or implied. See the License for the
+ specific language governing permissions and limitations
+ under the License.
+-->
+
+Apache HttpComponents
+=====================
+
+The Apache HttpComponents project is responsible for creating and maintaining a toolset of low level Java components
+focused on HTTP and associated protocols.
+
+This project functions under the Apache Software Foundation (http://www.apache.org), and is part of a larger community
+of developers and users.
+
+HttpComponents Overview
+-----------------------
+
+The Hyper-Text Transfer Protocol (HTTP) is perhaps the most significant protocol used on the Internet today. Web
+services, network-enabled appliances and the growth of network computing continue to expand the role of the HTTP
+protocol beyond user-driven web browsers, while increasing the number of applications that require HTTP support.
+
+Designed for extension while providing robust support for the base HTTP protocol, the HttpComponents may be of interest
+to anyone building HTTP-aware client and server applications such as web browsers, web spiders, HTTP proxies, web
+service transport libraries, or systems that leverage or extend the HTTP protocol for distributed communication.
+
+HttpComponents Structure
+-----------------------
+
+### HttpComponents Core
+
+[HttpCore](./httpcomponents-core-ga/) is a set of low level HTTP transport components that can be used to build custom
+client and server side HTTP services with a minimal footprint. HttpCore supports two I/O models: blocking I/O model
+based on the classic Java I/O and non-blocking, event driven I/O model based on Java NIO.
+
+### HttpComponents Client
+
+[HttpClient](./httpcomponents-client-ga/) is a HTTP/1.1 compliant HTTP agent implementation based on HttpCore. It also
+provides reusable components for client-side authentication, HTTP state management, and HTTP connection management.
+HttpComponents Client is a successor of and replacement for
+[Commons HttpClient 3.x](http://hc.apache.org/httpclient-legacy/index.html). Users of Commons HttpClient are strongly
+encouraged to upgrade.
+
+### Commons HttpClient (legacy)
+
+Commons HttpClient 3.x codeline is at the end of life. All users of Commons HttpClient 3.x are strongly encouraged to
+upgrade to HttpClient 4.1.
diff --git a/src/site/markdown/mail.md b/src/site/markdown/mail.md
new file mode 100644
index 0000000..7ba82d4
--- /dev/null
+++ b/src/site/markdown/mail.md
@@ -0,0 +1,190 @@
+<!--
+ Licensed to the Apache Software Foundation (ASF) under one
+ or more contributor license agreements. See the NOTICE file
+ distributed with this work for additional information
+ regarding copyright ownership. The ASF licenses this file
+ to you under the Apache License, Version 2.0 (the
+ "License"); you may not use this file except in compliance
+ with the License. You may obtain a copy of the License at
+
+ http://www.apache.org/licenses/LICENSE-2.0
+
+ Unless required by applicable law or agreed to in writing,
+ software distributed under the License is distributed on an
+ "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+ KIND, either express or implied. See the License for the
+ specific language governing permissions and limitations
+ under the License.
+-->
+
+HttpComponents Mailing Lists
+============================
+
+About Mailing Lists
+-------------------
+
+A mailing list is an electronic discussion forum that you can subscribe to. Once you are subscribed, you will receive
+every email that is sent to the list, and you can send mails to the list yourself. Every mail you send there will be
+received by hundreds, maybe thousands of subscribers. It will also become available in public archives indefinitely.
+
+Please note that usage of these mailing lists is subject to the
+[Public Forum Archive Policy](http://www.apache.org/foundation/public-archives.html)
+
+**Please** take a few minutes to read this page, in order to avoid annoyance for other subscribers, and embarrassment
+for yourself. There is a common set of etiquette guidelines for internet forums, sometimes called _netiquette_. You
+should be aware of these and try to observe them, here as well as in other forums.
+
+Eric S. Raymond and Rick Moen have written an article
+called ["How To Ask Questions The Smart Way"](http://www.catb.org/~esr/faqs/smart-questions.html) about mailing list
+netiquette. It's a long read, but worth the effort.
+
+**Note:** Please do NOT send your HttpComponents questions to the two authors. They welcome feedback on the article
+itself, but are simply not a help resource for HttpComponents.
+
+Research First
+--------------
+
+Before you post a question to a mailing list, make sure it isn't already answered. Read the available documentation.
+Search the web, and in particular the mailing list archives. Being answered with a link to a mail or FAQ entry that
+addresses exactly your question is one of the embarrassments you should avoid.
+
+If you are answered with a link to a mail, don't take it too hard either. Maybe you didn't know the correct terms to
+search for, or the mail was sent on another list. People that follow a mailing list for a long time are bound to
+remember some of the old mails, and it may be easier for them to locate the old mail than to write down the answer
+again.
+
+Choose The Appropriate Forum
+----------------------------
+
+Different kinds of questions are discussed in different forums. It is important to choose the right forum for your
+question. Posting a question to the wrong forum reduces your chances of getting a useful response. You will reach fewer
+people that can answer your question, and those that could, will be less inclined to do so.
+
+**Do not cross-post.** Do not send your question to more than one list. If you are in doubt where to post your question,
+it is better to pick the wrong list than to send it to several lists. Even if you get answers on more than one list,
+people subscribed to only one list will not be able to follow the whole discussion. Mailing list archives will also
+contain only fragments of the discussion, so that it becomes harder for others with the same question to find the
+answer.
+
+The article mentioned above has a section
+called ["Choose your forum carefully"](http://www.catb.org/~esr/faqs/smart-questions.html#forum). It basically tells you
+the same stuff you'll find below.
+
+### User List
+
+If you develop an application that _uses_ HttpClient, and you need advice on how to achieve something with it, post your
+question to the `httpclient-users` list. If you don't know whether HttpClient can do what you want it to do, post your
+question to the users list. Even though you are a developer, you are not a developer of the HttpComponents. So please
+don't post your question to the developer list.
+
+And if somebody else asks a question you can answer, please do so!
+
+### Developer List
+
+If you want to discuss _development of HttpComponents_, post your question or suggestion to the `dev` list. The
+developer list is used to discuss architecture, API design, new features, and bugs. Bug reports and comments filed
+in [JIRA](./issue-tracking.html) will automatically be sent to this list, too.
+
+### Issue Tracking
+
+We are using [JIRA](./issue-tracking.html) as our issue tracking system. Although this is not a mailing list, and should
+not be abused as a general discussion forum, it is another way to contact the HttpComponent developers. All issues and
+comments will be sent to the developer mailing list.
+
+If you are absolutely sure that you have found a bug, you can open a new issue for it. Choose "Bug" as the issue type.
+If you are absolutely sure that our components don't provide a feature that would be useful for you and others, you can
+open a new issue for it. Choose "New Feature" or "Wish" for it.
+
+If you are not absolutely sure, please ask on the appropriate mailing list first. Most developers are monitoring both
+lists, and we will tell you if you should open a new issue.
+
+### Personal Mail
+
+**Never** send a question directly to one of the people you have seen active on the mailing lists, or whose email
+address you've found in the source code. You will be scorned and rebuffed, or at best ignored.
+
+HttpComponents, as any other Apache project, is a _community_. Questions asked on a mailing list can be answered by any
+member of the community who knows the answer and has the time to write it down. Answers sent to a mailing list are
+available to everyone, through the public mailing list archives. This benefits the whole community.
+
+By sending a question directly to somebody, you are implying that this person alone is responsible for helping you out,
+and only you. No, we're not. We participate in a community. Post your question to the community at large, and chances
+are that one of the members will answer it. If that requires information that is of little interest to the community,
+for example large log files, you will be _asked_ to send such information directly to the person that picked up your
+question.
+
+It's OK to send a "Thank You" mail to a person that helped you. Just make sure that your next question goes to the
+mailing list again.
+
+### Shape Your Mail
+
+Some people reading your mail will be processing dozens or hundreds of mails daily. To get their attention and a quick
+reply, it is important that you make your mail easy to read and that you provide the background information that is
+needed to answer your question. The biggest part of the article on
+[asking smart questions](http://www.catb.org/~esr/faqs/smart-questions.html) mentioned above addresses this problem, so
+we'll only give you the highlights here.
+
+- Choose a descriptive Subject for your mail. Not:
+ ```
+ "Help! URGENT: Problem with HttpClient!!!"
+ ```
+ This subject does not give the least indication of what your mail is about. So you have a problem with HttpClient? And
+ you need help? Duh, why else would you post to the mailing list. And it's urgent? For you maybe, but not for anyone
+ else here.
+
+- **Don't send HTML mail**, or other stylized mails. Use plain text. Either format it with about 72 characters per line,
+ or just type without linebreaks so automatic formatters can take care of it. Don't format your mails with 90
+ characters per line. Automatic formatters will split each line, making the result very hard to read.
+
+- **Get to the point.**
+ Ideally, keep your mail short. Just describe the problem and give the necessary background information. If it's read
+ in less than a minute, many people will read it and the answer can probably be given quickly as well. If it takes
+ several minutes to read your mail, people will take care of other mails first, and may never bother to read yours. If
+ you have to provide extensive background information, make sure to get to the point in the first paragraph. The one
+ that can be read in less than a minute. Describe your problem there, so people can decide quickly whether it makes
+ sense for them to read the rest.
+
+* **Don't Reply to send a new question.**
+ If you have an answer or otherwise want to join an ongoing discussion, then use Reply-To on another mail. If you have
+ a new question or want to start a new discussion, do not reply to a mail you've received from the list. Even if you
+ change the subject, your mail client would still flag it as belonging to the existing thread. Many archives and email
+ clients provide a threaded view, where only the initial mail of a thread is shown by default. Your mail will just get
+ ignored by the people not interested in the original thread, even though they might be able to help you.
+
+### The Lists
+
+The HttpComponents project currently uses the following lists. Clicking on a list name will take you to a page with
+subscribe, unsubscribe, and archive information. See below for information on digests.
+
+* [httpclient-users](./mail-lists.html) - The list for users of HttpClient, either version 3 or 4. Users of HttpCore can
+ also post their questions here, although most subscribers will probably not be able to answer them.
+
+* [dev](./mail-lists.html) - The list for developers of HttpComponents and HttpClient 3. We don't mind getting HttpCore
+ user questions here. Our issues tracker JIRA also posts here.
+
+* [commits](./mail-lists.html) - The list for messages from our source code repository. Whenever the source code is
+ modified, a mail with the changes is sent. This list is read-only. HttpComponents committers are expected to subscribe
+ to the commits list, so they can review the changes.
+
+* _private_ - The list for private communication of the HttpComponents PMC. Only PMC members and ASF members can
+ subscribe. There is no public archive.
+
+### Subscribe And Unsubscribe
+
+To subscribe to the list `<xxx>`, send a mail to `<xxx>-subscribe@hc.apache.org`. While you are subscribed, you will
+receive all mails sent to the list. You can send mails to the list yourself using the address `<xxx>@hc.apache.org`.
+This does not apply for the commits list, where only the source code repository is allowed to send mails.
+
+To unsubscribe from the list `<xxx>`, send a mail to`<xxx>-unsubscribe@hc.apache.org`. Unsubscribe information is also
+appended to every mail sent via the list.
+
+The **digest** of a list collects all mails of that list, sending you occasional updates. Each update contains the
+subjects of the recent mails, and the mails themselves as attachments. This significantly reduces the number of
+individual mails you receive from the list, while still giving you access to all the information.
+
+To subscribe to the digest of list `<xxx>`, send a mail to`<xxx>-digest-subscribe@hc.apache.org`. While you are
+subscribed to the digest, you can send mails to the list itself using the address`<xxx>@hc.apache.org`. This does not
+apply for the commits list, where only the source code repository is allowed to send mails.
+
+To unsubscribe from the digest of list `<xxx>`, send a mail to `<xxx>-digest-unsubscribe@hc.apache.org`. Unsubscribe
+information is also appended to every mail sent by the digest.
diff --git a/src/site/markdown/news.md b/src/site/markdown/news.md
new file mode 100644
index 0000000..87164fc
--- /dev/null
+++ b/src/site/markdown/news.md
@@ -0,0 +1,1215 @@
+<!--
+ Licensed to the Apache Software Foundation (ASF) under one
+ or more contributor license agreements. See the NOTICE file
+ distributed with this work for additional information
+ regarding copyright ownership. The ASF licenses this file
+ to you under the Apache License, Version 2.0 (the
+ "License"); you may not use this file except in compliance
+ with the License. You may obtain a copy of the License at
+
+ http://www.apache.org/licenses/LICENSE-2.0
+
+ Unless required by applicable law or agreed to in writing,
+ software distributed under the License is distributed on an
+ "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+ KIND, either express or implied. See the License for the
+ specific language governing permissions and limitations
+ under the License.
+-->
+
+HttpComponents Project News
+===========================
+
+###### 12 February 2021 - HttpComponents Client 5.1-beta1 released
+
+This is the first BETA release in the 5.1 release series that includes a number of new features as well performance
+optimizations in the classic HTTP transport.
+
+Notable changes and features included in the 5.1 series:
+
+- Conditional conformance with RFC 3986 (Uniform Resource Identifier (URI): Generic Syntax).
+- Improved support for out of sequence response message handing by the classic (blocking) HTTP transport.
+
+###### 8 February 2021 - HttpComponents Core 5.1-beta3 released
+
+This is likely the last BETA release in the 5.1 release series. The next release is expected to be 5.1 GA. This beta
+includes a number of new features as well as bug fixes from the stable 5.0.x branch.
+
+Notable changes and features included in the 5.1 series:
+
+- Conditional conformance with RFC 3986 (Uniform Resource Identifier (URI): Generic Syntax).
+- Improved support for out of sequence response message handing by the classic (blocking) HTTP transport.
+
+###### 3 December 2020 - HttpComponents Core 5.1-beta2 released
+
+This is the second BETA release in the 5.1 release series that includes a number of new features as well as bug fixes
+from the stable 5.0.x branch.
+
+###### 3 December 2020 - HttpComponents Core 5.0.3 (GA) released
+
+This is a maintenance release that corrects a number of defects discovered since release 5.0.2 including a defect in the
+async (non-blocking) transport potentially causing an infinite event loop and and excessive CPU utilization.
+
+###### 1 December 2020 - HttpComponents Core 4.4.14 (GA) released
+
+This is a maintenance release that corrects a number of defects discovered since release 4.4.13 including two defects in
+the async (non-blocking) transport potentially causing an infinite event loop and and excessive CPU utilization.
+
+###### 8 October 2020 - HttpComponents Client 5.0.3 (GA) released
+
+This is a maintenance release that fixes incorrect handling of malformed authority component in request URIs.
+
+###### 8 October 2020 - HttpComponents Client 4.5.13 (GA) released
+
+This is a maintenance release that fixes incorrect handling of malformed authority component in request URIs.
+
+###### 28 September 2020 - HttpComponents Client 5.0.2 (GA) released
+
+This is a maintenance release that upgrades HttpCore to the latest version and addresses a number of issues found since
+5.0.1 release.
+
+###### 21 September 2020 - HttpComponents Core 5.1-beta1 released
+
+This is the first BETA release in the 5.1 release series that includes a number of new features as well performance
+optimizations in the classic HTTP transport.
+
+###### 13 September 2020 - HttpComponents Core 5.0.2 (GA) released
+
+This release reverts changes to early response handling logic introduced in 5.0.1 and fixes a number of minor defects.
+Improvement of the early response handling by the classic client protocol handler has been moved to 5.1.
+
+###### 15 June 2020 - HttpComponents Client 5.0.1 (GA) released
+
+This is a maintenance release that upgrades HttpCore to the latest version and addresses a number of issues found since
+5.0 release.
+
+###### 10 June 2020 - HttpComponents Core 5.0.1 (GA) released
+
+This is a maintenance release that improves handling of early response messages by the classic client protocol handler
+and fixes a number of minor defects.
+
+###### 9 March 2020 - HttpComponents Client 4.5.12 (GA) released
+
+This is a maintenance release that fixes a regression introduced by the previous release that caused rejection of
+certificates with non-standard domains.
+
+###### 24 February 2020 - HttpComponents Client 5.0 (GA) released
+
+This is the first stable (GA) release of HttpClient 5.0.
+
+Notable changes and features included in the 5.0 series are:
+
+- Support for the HTTP/2 protocol and conformance to requirements and recommendations of the latest HTTP/2 protocol
+ specification documents
+ (RFC 7540, RFC 7541.)
+
+ Supported features:
+ - HPACK header compression
+ - Stream multiplexing (client and server)
+ - Flow control
+ - Response push
+ - Message trailers
+ - Expect-continue handshake
+ - Connection validation (ping)
+ - Application-layer protocol negotiation (ALPN)
+ - TLS 1.2 security features
+
+- Improved conformance to requirements and recommendations of the latest HTTP/1.1 protocol specification documents (
+ RFC 7230, RFC 7231.)
+- New connection pool implementation with lax connection limit guarantees and better performance under higher
+ concurrency due to absence of a global pool lock.
+- Support for Reactive Streams API http://www.reactive-streams.org/
+- Package name space changed to 'org.apache.hc.client5'.
+- Maven group id changed to 'org.apache.httpcomponents.client5'.
+
+HttpClient 5.0 releases can be co-located with earlier major versions on the same classpath due to the change in package
+names and Maven module coordinates.
+
+###### 18 February 2020 - HttpComponents Core 5.0 (GA) released
+
+This is the first stable (GA) release of HttpCore 5.0.
+
+Notable changes and features included in the 5.0 series:
+
+- Support for HTTP/2 protocol and conformance to requirements and recommendations of the latest HTTP/2 protocol
+ specification (RFC 7540, RFC 7541)
+
+ Supported features:
+ - HPACK header compression
+ - stream multiplexing (client and server)
+ - flow control
+ - response push (client and server)
+ - message trailers
+ - expect-continue handshake
+ - connection validation (ping)
+ - application-layer protocol negotiation (ALPN) on Java 9+
+ - TLS 1.2 security features
+
+ Features out of scope for 5.0 release:
+
+ - padding of outgoing frames
+ - stream priority
+ - plain connection HTTP/1.1 upgrade
+ - CONNECT method
+
+- Improved conformance to requirements and recommendations of the latest HTTP/1.1 protocol specification (RFC 7230, RFC
+ 7231)
+- New asynchronous HTTP transport APIs consistent for both HTTP/1.1 and HTTP/2 transport.
+- Redesigned I/O reactor APIs and improved NIO based reactor implementation for a greater performance and scalability.
+- Support for server-side request filters for classic and asynchronous server implementations. Request filters could be
+ used to implement cross-cutting protocol aspects such as the 'expect-continue' handshaking and user authentication /
+ authorization.
+- Support for Reactive Streams API http://www.reactive-streams.org/
+- Redesigned connection pool implementation with strict connection limit guarantees. The connection pool is expected to
+ have a better performance under higher concurrency due to reduced global pool lock contention.
+- New connection pool implementation with lax connection limit guarantees and better performance under higher
+ concurrency due to absence of a global pool lock.
+- Package name space changed to 'org.apache.hc.core5'
+
+- Maven group id changed to 'org.apache.httpcomponents.core5'
+
+###### 27 January 2020 - HttpComponents Client 5.0-beta7 released
+
+This BETA release upgrades HttpCore to the latest version and addresses a number of issues found since the previous BETA
+release.
+
+###### 20 January 2020 - HttpComponents Client 4.5.11 (GA) released
+
+This is a maintenance release that fixes a number defects discovered since 4.5.10 and upgrades HttpCore dependency to
+version 4.4.13.
+
+###### 14 January 2020 - HttpComponents Core 4.4.13 (GA) released
+
+This is a maintenance release that corrects a number of defects discovered since release 4.4.12.
+
+###### 8 January 2019 - HttpComponents HttpCore 5.0-beta11 released
+
+This BETA fixes HTTP/2 SETTINGS_HEADER_TABLE_SIZE negotiation and HTTP/2 connection window management logic as well as
+fixes a number of other defects found since the last release.
+
+###### 31 October 2019 - HttpComponents HttpCore 5.0-beta10 released
+
+This BETA fixes a bug in the HTTP/2 setting handshake implementation and a performance regression in HTTP/1.1 protocol
+handler.
+
+###### 10 October 2019 - HttpComponents HttpClient 5.0-beta6 released
+
+This BETA release picks up the latest fixes and performance improvements from HttpCore and addresses a number of issues
+found since the previous BETA release.
+
+###### 7 October 2019 - HttpComponents HttpCore 5.0-beta9 released
+
+This BETA fixes a number of defects found since the last release, improves behavior of the lax (concurrent) connection
+pools, simplifies and improves input event handling of SSL/TLS sessions and the HTTP/1.1 protocol event handler.
+
+###### 10 Sept 2019 - HttpComponents Client 4.5.10 (GA) released
+
+This is a maintenance release that corrects a number of defects discovered since release 4.5.9.
+
+###### 5 Sept 2019 - HttpComponents Core 4.4.12 (GA) released
+
+This is a maintenance release that corrects a number of defects discovered since release 4.4.11.
+
+###### 22 July 2019 - HttpComponents HttpClient 5.0-beta5 released
+
+This BETA release picks up the latest fixes and performance improvements from HttpCore and addresses a number of issues
+found since the previous BETA release.
+
+###### 15 July 2019 - HttpComponents HttpCore 5.0-beta8 released
+
+This BETA fixes a number of defects found since the last release and adds several convenience factory and builder
+classes, mainly for TLS configuration and HTTP message construction.
+
+Notable new features in this release:
+
+- As of this version all server and requester implementations exclude weak TLS protocol versions and ciphers.
+
+###### 12 June 2019 - HttpComponents HttpClient 4.5.9 (GA) released
+
+This is a maintenance release that fixes a number defects discovered since 4.5.8.
+
+###### 8 April 2019 - HttpComponents HttpClient 5.0-beta4 released
+
+This BETA release picks up the latest fixes and performance improvements from HttpCore and addresses a number of issues
+found since the previous BETA release.
+
+Notable features in this release:
+
+- Security improvements.
+- URI handling improvements.
+
+###### 31 March 2019 - HttpComponents HttpClient 4.5.8 (GA) released
+
+This is a maintenance release that makes request URI normalization configurable on per request basis and also ports
+several improvements in URI handling from HttpCore master.
+
+###### 4 March 2019 - HttpComponents HttpCore 5.0-beta7 released
+
+This BETA release adds support for SOCKS version 5, improves support for TLS handshake timeout configuration, improves
+URI builder, and fixes various defects.
+
+Notable new features in this release:
+
+- SOCKS version 5 support
+- Improved TLS handshake timeout configuration
+
+###### 24 January 2019 - HttpComponents HttpClient 4.5.7 (GA) released
+
+This is a maintenance release that corrects Automatic-Module-Name definitions added in the previous release and fixes a
+number of minor defects discovered since 4.5.6.
+
+###### 21 January 2019 - HttpComponents HttpCore 4.4.11 (GA) released
+
+This is a maintenance release that corrects a number of defects in non-blocking SSL session code that caused
+compatibility issues with TLSv1.3 protocol implementation shipped with Java 11.
+
+###### 17 December 2018 - HttpComponents HttpClient 5.0-beta3 released
+
+This BETA release adds support for advanced TLS functions (such as ALPN protocol negotiation)
+on Java 1.7 and Java 1.8 through Conscrypt TLS library and picks up the latest fixes and performance improvements from
+HttpCore.
+
+Notable new features in this release:
+
+- TLS ALPN protocol negotiation support on older JREs through Conscrypt TLS library.
+
+###### 6 December 2018 - HttpComponents HttpCore 5.0-beta6 released
+
+This BETA release adds support for advanced TLS functions (such as ALPN protocol negotiation)
+on Java 1.7 and Java 1.8 through Conscrypt TLS library, and fixes a number of defects found since the previous release.
+
+Notable new features in this release:
+
+- TLS ALPN protocol negotiation on Java 1.7 and Java 1.8 through Conscrypt TLS library
+
+###### 29 October 2018 - HttpComponents HttpClient 5.0-beta2 released
+
+This BETA release resolves compatibility issues with Java 11 new TLS engine as well as a number of defects found since
+the previous release.
+
+Notable new features in this release:
+
+- JDK 11 compatibility
+- Support for request specific push consumers
+- Support for Reactive Streams API http://www.reactive-streams.org/
+
+###### 22 October 2018 - HttpComponents HttpCore 5.0-beta5 released
+
+This BETA release adds support for Reactive Streams API [http://www.reactive-streams.org/]
+and fixes compatibility issues with Java 11 new TLS engine as well as a number of defects found since the previous
+release.
+
+This release also includes a redesigned HTTP stress test tool loosely based on Apache Benchmark (AB) command interface
+with support for HTTP/2.
+
+###### 29 August 2018 - HttpComponents HttpCore 5.0-beta3 released
+
+This BETA release fixes a number of defects found since the previous release, adds several incremental improvements and
+improves javadoc documentation.
+
+###### 23 July 2018 - HttpComponents HttpAsyncClient 4.1.4 (GA) released
+
+This is a maintenance release that adds Automatic-Module-Name to the manifest for compatibility with Java 9 Platform
+Module System and fixes a number of issues discovered since 4.1.3.
+
+###### 9 July 2018 - HttpComponents HttpClient 4.5.6 (GA) released
+
+This is a maintenance release that adds Automatic-Module-Name to the manifest for compatibility with Java 9 Platform
+Module System and fixes a number of issues discovered since 4.5.5.
+
+###### 3 July 2018 - HttpComponents HttpCore 4.4.10 (GA) released
+
+This is a maintenance release that adds Automatic-Module-Name to the manifest for compatibility with Java 9 Platform
+Module System and fixes a number of issues discovered since 4.4.9.
+
+###### 22 January 2018 - HttpComponents HttpClient 4.5.5 GA released
+
+This is a maintenance release that fixes a regression introduced by the previous release causing a NPE in
+SystemDefaultCredentialsProvider.
+
+###### 18 January 2018 - HttpComponents HttpClient 5.0-beta1 released
+
+This is the first BETA release of HttpClient 5.0. The 5.0 release serices introduces support for the HTTP/2 protocol and
+event driven messaging APIs consistent for all supported HTTP protocol versions.
+
+HttpClient ships with two client implementations:
+
+- HttpClient Classic is based on the classic (blocking) I/O model; largely compatible with the 4.x APIs; supports
+ HTTP/1.1 only.
+- HttpClient Async is based on NIO model; new event driven APIs consistent for all supported HTTP protocol versions;
+ supports both HTTP/1.1 and HTTP/2.
+
+Notable new features in this release:
+
+- New asynchronous HTTP cache backend APIs
+- Fully asynchronous HTTP cache backend based on Memcached
+- Support for bulk cache retrieval
+
+###### 15 January 2018 - HttpComponents HttpCore 5.0-beta2 released
+
+This BETA release fixes a number of defects found since the previous release and adds several incremental improvements.
+
+###### 11 January 2018 - HttpComponents HttpCore 4.4.9 (GA) released
+
+This is a maintenance release that fixes a number of issues discovered since 4.4.8 and adds a few low-level methods.
+
+###### 4 December 2017 - HttpComponents HttpClient 4.5.4 (GA) released
+
+This is a maintenance release that fixes a number of issues discovered since release 4.5.3.
+
+###### 27 November 2017 - HttpComponents HttpClient 5.0-alpha3 released
+
+This is a major release that introduces support for the HTTP/2 protocol and event driven messaging APIs consistent for
+all supported HTTP protocol versions.
+
+Notable new features in this release:
+
+- Asynchronous HttpClient implementations optimized for HTTP/2 multiplexed request execution.
+- Full support for HTTP caching by asynchronous HttpClient implementations including streaming message exchanages.
+
+###### 6 November 2017 - HttpComponents HttpCore 5.0-beta1 released
+
+This is a major release that renders HttpCore API incompatible with the stable 4.x branch and upgrades HTTP/1.1 and
+HTTP/2 protocol conformance to the requirements and recommendations of the latest protocol specification.
+
+Notable new features in this release:
+
+- New HTTP/2 requester optimized for multiplexed execution of requests.
+
+###### 7 October 2017 - HttpComponents HttpCore 4.4.8 (GA) released
+
+This is a maintenance release that fixes a number of issues discovered since release 4.4.7.
+
+###### 14 September 2017 - HttpComponents HttpCore 4.4.7 (GA) released
+
+This is a maintenance release that fixes a number of issues discovered since release 4.4.6.
+
+###### 4 September 2017 - HttpComponents HttpCore 5.0-alpha4 released
+
+This is a major release that renders HttpCore API incompatible with the stable 4.x branch and upgrades HTTP/1.1 and
+HTTP/2 protocol conformance to the requirements and recommendations of the latest protocol specification.
+
+###### 11 May 2017 - HttpComponents HttpClient 5.0-alpha2 released
+
+This is a major release that introduces support for HTTP/2 protocol and event driven messaging APIs consistent for all
+supported HTTP protocol versions.
+
+###### 2 May 2017 - HttpComponents HttpCore 5.0-alpha3 released
+
+This is a major release that renders HttpCore API incompatible with the stable 4.x branch and upgrades HTTP/1.1 and
+HTTP/2 protocol conformance to the requirements and recommendations of the latest protocol specification.
+
+###### 10 February 2017 - HttpComponents HttpAsyncClient 4.1.3 (GA) released
+
+This is a maintenance release that fixes a number of issues discovered since release 4.1.2.
+
+###### 27 January 2017 - HttpComponents HttpClient 4.5.3 (GA) released
+
+This is a maintenance release that fixes a number of issues discovered since release 4.5.2.
+
+###### 12 January 2017 - HttpComponents HttpCore 4.4.6 (GA) released
+
+This is a maintenance release that fixes a number of issues discovered since release 4.4.5.
+
+###### 27 December 2016 - HttpComponents HttpCore 5.0-alpha2 released
+
+This is a major release that renders HttpCore API incompatible with the stable 4.x branch and upgrades HTTP/1.1 and
+HTTP/2 protocol conformance to the requirements and recommendations of the latest protocol specification.
+
+###### 27 June 2016 - HttpComponents HttpAsyncClient 4.1.2 (GA) released
+
+This is a maintenance release that fixes a number of issues discovered since release 4.1.1.
+
+###### 14 June 2016 - HttpComponents HttpCore 4.4.5 (GA) released
+
+This is a maintenance release that fixes a number of issues discovered since release 4.4.4.
+
+###### 1 March 2016 - HttpComponents HttpClient 4.5.2 (GA) released
+
+This is a maintenance release that fixes a number of minor bugs reported since 4.5.1.
+
+###### 28 January 2016 - HttpComponents HttpClient 5.0-alpha1 released
+
+This is a major release that renders HttpClient API incompatible with the stable 4.x branch and upgrades HTTP/1.1
+protocol conformance to the requirements and recommendations of the latest protocol specification. This release lays the
+foundation for transition to HTTP/2 as the primary transport protocol in the future releases.
+
+###### 3 January 2016 - HttpComponents HttpCore 5.0-alpha1 released
+
+This is a major release that renders HttpCore API incompatible with the stable 4.x branch and upgrades HTTP/1.1 protocol
+conformance to the requirements and recommendations of the latest protocol specification. This release lays the
+foundation for transition to HTTP/2 as the primary transport protocol in the future releases.
+
+###### 9 November 2015 - HttpComponents HttpAsyncClient 4.1.1 (GA) released
+
+This is a maintenance release that fixes a number of issues discovered since release 4.1 and upgrades HttpCore and
+HttpClient dependencies.
+
+###### 4 November 2015 - HttpComponents HttpCore 4.4.4 (GA) released
+
+This is a maintenance release that fixes a number of issues discovered since release 4.4.3.
+
+###### 16 September 2015 - HttpComponents HttpClient 4.5.1 (GA) released
+
+This is a maintenance release that fixes a number of minor bugs reported since 4.5.
+
+###### 11 September 2015 - HttpComponents HttpCore 4.4.3 (GA) released
+
+This maintenance release fixes a bug in non-blocking HTTP request pipelining code discovered since 4.3.1.
+
+###### 5 June 2015 - HttpClient 4.5 (GA) released
+
+HttpClient 4.5 (GA) is a minor feature release that includes several incremental enhancements to the exisitng
+functionality such as support for private domains in the Mozilla Public Suffix List.
+
+###### 23 April 2015 - HttpAsyncClient 4.1 (GA) released
+
+This is the first stable (GA) release of HttpAsyncClient 4.1. Notable features and enhancements included in 4.1 series
+are:
+
+- Support for pipelined request execution
+- Support for the latest HTTP state management specification (RFC 6265). Please note that the old cookie policy is still
+ used by default for compatibility reasons. RFC 6265 compliant cookie policies need to be explicitly configured by the
+ user. Please also note that as of next feature release support for Netscape draft, RFC 2109 and RFC 2965 cookie
+ policies will be deprecated and disabled by default. It is recommended to use RFC 6265 compliant policies for new
+ applications unless compatibility with RFC 2109 and RFC 2965 is required and to migrate existing applications to the
+ default cookie policy.
+- Enhanced, redesigned and rewritten default SSL hostname verifier with improved RFC 2818 compliance
+- Default SSL hostname verifier and default cookie policy now validate certificate identity and cookie domain of origin
+ against the public suffix list maintained by Mozilla.org
+ <https://publicsuffix.org/list>
+- Authentication cache thread-safety: authentication cache used by HttpClient is now thread-safe and can be shared by
+ multiple threads in order to re-use authentication state for subsequent requests
+
+###### 31 March 2015 - HttpComponents HttpClient 4.4.1 (GA) released
+
+This is a maintenance release that fixes a number of bugs reported since 4.4.
+
+###### 20 March 2015 - HttpComponents HttpCore 4.4.1 (GA) released
+
+This is a maintenance release that fixes a number of minor bugs found since 4.4.
+
+###### 5 February 2015 - HttpComponents HttpClient 4.4 released
+
+This is the first stable (GA) release of HttpClient 4.4. Notable features and enhancements included in 4.4 series are:
+
+- Support for the latest HTTP state management specification (RFC 6265). Please note that the old cookie policy is still
+ used by default for compatibility reasons. RFC 6265 compliant cookie policies need to be explicitly configured by the
+ user. Please also note that as of next feature release support for Netscape draft, RFC 2109 and RFC 2965 cookie
+ policies will be deprecated and disabled by default. It is recommended to use RFC 6265 compliant policies for new
+ applications unless compatibility with RFC 2109 and RFC 2965 is required and to migrate existing applications to the
+ default cookie policy.
+- Enhanced, redesigned and rewritten default SSL hostname verifier with improved RFC 2818 compliance
+- Default SSL hostname verifier and default cookie policy now validate certificate identity and cookie domain of origin
+ against the public suffix list maintained by Mozilla.org
+ <https://publicsuffix.org/list>
+- More efficient stale connection checking: indiscriminate connection checking which results in approximately 20 to 50
+ ms overhead per request has been deprecated in favor of conditional connection state validation (persistent
+ connections are to be re-validated only if a specified period inactivity has elapsed)
+- Authentication cache thread-safety: authentication cache used by HttpClient is now thread-safe and can be shared by
+ multiple threads in order to re-use authentication state for subsequent requests
+- Native Windows Negotiate and NTLM via SSPI through JNA: when running on Windows OS HttpClient configured to use native
+ NTLM or SPNEGO authentication schemes can make use of platform specific functionality via JNA and current user
+ credentials. This functionality is still considered experimental, known to have compatibility issues and subject to
+ change without prior notice.
+
+###### 17 December 2014 - HttpComponents HttpCore 4.4 released
+
+This is the first stable (GA) release of HttpCore 4.4. The most notable features included in 4.4 series are:
+
+- Support for pipelined request processing on the server side
+- Support for pipelined request execution on the client side
+- Simplified bootstrapping of blocking and non-blocking (NIO) HTTP server implementations
+- Inclusion of SSL context initialization utilities from HttpClient
+
+###### 6 November 2014 - HttpComponents HttpClient 4.3.6 (GA) released
+
+This is a maintenance release that fixes several problems with HttpClient OSGi bundle as well as some other issues
+reported since release 4.3.5.
+
+Please note that as of this release HttpClient disables all versions of SSL (including SSLv3)
+in favor of the TLS protocol by default. Those users who wish to continue using SSLv3 need to explicitly enable support
+for it.
+
+###### 22 October 2014 - HttpComponents HttpCore 4.3.3 (GA) released
+
+This maintenance release fixes a number of bugs found since 4.3.2, mostly in the NIO transport components. All users of
+HttpCore 4.3 are advised to upgrade.
+
+###### 17 October 2014 - HttpComponents HttpAsyncClient 4.4-beta1 released
+
+This is the first BETA release of HttpAsyncClient 4.1. Notable features and enhancements included in 4.1 series are:
+
+- Support for pipelined request execution
+- Enhanced redesigned and rewritten default SSL hostname verifier with improved RFC 2818 compliance
+- Default SSL hostname verifier and default cookie policy now validate certificate identity and cookie domain of origin
+ against the public suffix list maintained by Mozilla.org
+ <https://publicsuffix.org/list>
+- Authentication cache thread-safety: authentication caches used by HttpAsyncClient is now thread-safe and can be shared
+ by multiple contexts in order to re-use authentication state for subsequent requests
+
+###### 28 September 2014 - HttpComponents HttpClient 4.4-beta1 released
+
+This is the first BETA release of HttpClient 4.4. Notable features and enhancements included in 4.4 series are:
+enhanced redesigned and rewritten default SSL hostname verifier with improved RFC 2818 compliance; default SSL hostname
+verifier and default cookie policy now validate certificate identity and cookie domain of origin against the public
+suffix list maintained by Mozilla.org; native windows Negotiate/NTLM via JNA; more efficient stale connection checking;
+authentication cache thread-safety
+
+###### 22 September 2014 - HttpComponents HttpCore 4.4-beta1 released
+
+This is the first BETA release from the 4.4.x development branch. The most notable features included in 4.4 series are:
+support for pipelined request processing on the server side; support for pipelined request execution on the client side;
+simplified bootstrapping of blocking and non-blocking (NIO) HTTP server implementations.
+
+###### 10 Aug 2014 - HttpComponents HttpAsyncClient 4.0.2 (GA) released
+
+HttpAsyncClient 4.0.2 (GA) is a bug fix release that addresses several issues reported since release 4.0.1.
+
+###### 10 Aug 2014 - HttpComponents HttpClient 4.3.5 (GA) released
+
+HttpClient 4.3.5 (GA) is a bug fix release that addresses several issues reported since release 4.3.4.
+
+###### 30 June 2014 - HttpComponents HttpClient 4.4-alpha1 released
+
+This is the first ALPHA release from the 4.4.x development branch. Notable features and enhancements included this
+release are: more efficient stale connection checking, native Windows Negotiate/NTLM via JNA, authentication cache
+thread-safety
+
+###### 18 June 2014 - HttpComponents HttpCore 4.4-alpha1 released
+
+This is the first release from the 4.4.x development branch. The most notable features included in this release are:
+support for pipelined request processing on the server side, support for pipelined request execution on the client
+sides, simplified bootstrapping of blocking and non-blocking (NIO) HTTP server implementations
+
+###### 6 June 2014 - HttpComponents HttpClient 4.3.4 (GA) released
+
+HttpClient 4.3.4 (GA) is a maintenance release that improves performance in high concurrency scenarios. This version
+replaces dynamic proxies with custom proxy classes and eliminates thread contention in java.reflect.Proxy.newInstance()
+when leasing connections from the connection pool and processing response messages
+
+###### 26 February 2014 - HttpComponents HttpClient 4.3.3 (GA) released
+
+HttpClient 4.3.3 (GA) is a bug fix release that fixes a regression introduced by the previous release causing a
+significant performance degradation in compressed content processing.
+
+Users of HttpClient 4.3 are encouraged to upgrade.
+
+###### 24 February 2014 - HttpComponents HttpAsyncClient 4.0.1 (GA) released
+
+This maintenance release fixes a number of bugs including incorrect OSGi bundle metadata found since release 4.0. This
+release also upgrades HttpCore and HttpClient dependencies to the latest stable versions.
+
+Users of HttpAsyncClient 4.0 are advised to upgrade.
+
+###### 17 February 2014 - HttpComponents HttpCore 4.3.2 (GA) released
+
+This maintenance release fixes a number of bugs and regressions found since 4.3.1, mostly in the NIO transport
+components. All users of HttpCore 4.3 are advised to upgrade.
+
+###### 19 January 2014 - HttpComponents HttpClient 4.3.2 (GA) released
+
+HttpClient 4.3.2 (GA) is a maintenance release that delivers a number of improvements as well as bug fixes for issues
+reported since 4.3.1 release. SNI support for Oracle JRE 1.7+ is being among the most notable improvements.
+
+Users of HttpClient 4.3 are encouraged to upgrade.
+
+###### 27 December 2013 - HttpComponents HttpCore 4.3.1 (GA) released
+
+This maintenance release fixes a number of bugs and regressions found since 4.3, mostly in the NIO transport components.
+All users of HttpCore 4.3 are advised to upgrade.
+
+###### 31 October 2013 - HttpComponents HttpAsyncClient 4.0 (GA) released
+
+This is the first stable (GA) release of Apache HttpAsyncClient 4.0. HttpAsyncClient is a library for asynchronous
+client-side HTTP communication built on top of HttpCore NIO transport. It is a complementary library to Apache
+HttpClient intended and optimized for special cases whereby ability to scale to many thousands of concurrent connections
+is more important than performance in terms of raw data throughput.
+
+HttpAsyncClient 4.0 is designed to have similar APIs as Apache HttpClient 4.3 and a comparable feature set. In addition
+HttpAsyncClient provides full support for zero-copy file upload and download operations. It presently does not support
+transparent content decompression and automatic I/O error recovery. These features may be added in future releases.
+
+###### 7 October 2013 - HttpComponents HttpClient 4.3.1 (GA) released
+
+This is a maintenance release that addresses a number of issues reported since release 4.3, including one major security
+issue. Users of HttpClient 4.3 are strongly advised to upgrade.
+
+###### 12 September 2013 - HttpComponents HttpClient 4.3 (GA) released
+
+This is the first stable (GA) release of HttpClient 4.3. The 4.3 branch enhances HttpClient in several key areas and
+includes several notable features and improvements:
+
+- Support for Java 7 try-with-resources for resource management (connection release.)
+- Added fluent Builder classes for HttpEntity, HttpRequest, HttpClient and SSLContext instances.
+- Deprecation of preference and configuration API based on HttpParams interface in favor of constructor injection and
+ plain configuration objects.
+- Reliance on object immutability instead of access synchronization for thread safety. Several old classes whose
+ instances can be shared by multiple request exchanges have been replaced by immutable equivalents.
+- DefaultHttpClient, DecompressingHttpClient, CachingHttpClient and similar classes are deprecated in favor of builder
+ classes that produce immutable HttpClient instances.
+- HttpClient builders now dynamically construct a request execution pipeline tailored specifically to the user
+ configuration by physically excluding unnecessary protocol components.
+- There is now an option to construct a minimal HttpClient implementation that can only execute basic HTTP message
+ exchanges without redirects, authentication, state management or proxy support. This feature might be of particular
+ use in web crawler development.
+- There is now option to avoid strict URI syntax for request URIs by executing HTTP requests with an explicitly
+ specified target host. HttpClient will no longer attempt to parse the request URI if it does not need to extract the
+ target host from it.
+
+This release also includes all fixes from the stable 4.2.x release branch.
+
+###### 12 September 2013 - HttpComponents HttpClient 4.2.6 (GA) released
+
+This is a maintenance release that addresses a number of non-critical issues reported since release 4.2.5.
+
+###### 5 August 2013 - HttpComponents HttpCore 4.3 released
+
+This is the first stable (GA) release of HttpCore 4.3. The most notable features in the 4.3 branch are:
+
+- Deprecation of preference and configuration API based on HttpParams interface in favor of constructor injection and
+ plain configuration objects.
+- Reliance on object immutability instead of access synchronization for thread safety. Several old classes whose
+ instances can be shared by multiple request exchanges have been replaced by immutable equivalents.
+
+The 4.3 branch also contains performance optimizations such as reduced TCP packet fragmentation and more efficient lease
+/ release operations for pools of persistent connections on the client side.
+
+This release also includes all fixes from the 4.2.x release branch.
+
+###### 5 August 2013 - HttpComponents HttpCore 4.2.5 released
+
+This is a maintenance release that fixes a number of bugs found in NIO components since 4.2.4. Users of earlier versions
+of HttpCore 4.2 are advised to upgrade.
+
+This is likely to be the last release in the 4.2.x branch.
+
+###### 12 June 2013 - HttpComponents HttpClient 4.3-beta2 released
+
+This is the second BETA release of HttpClient 4.3. The 4.3 branch enhances HttpClient in several key areas and includes
+several notable features and improvements: Support for Java 7 try-with-resources for resource management (
+connection release); fluent Builder classes for HttpEntity, HttpRequest and HttpClient instances, deprecation of
+preference and configuration API based on HttpParams interface in favor of constructor injection and plain configuration
+objects, reliance on object immutability instead of access synchronization for thread safety.
+
+This release also includes all fixes from the stable 4.2.x release branch.
+
+###### 16 May - HttpComponents HttpAsyncClient 4.0-beta4 released
+
+The 4.0 BETA4 release delivers significant performance improvements in request execution, especially for short HTTP
+messages, and also re-aligns programming interfaces used by the library with HttpCore 4.3 and HttpClient 4.3 APIs.
+Configuration and preference APIs of HttpAsyncClient are now consistent with those used by HttpClient 4.3.
+
+###### 8 May - HttpComponents HttpCore 4.3-beta2 released
+
+This is the second BETA release from the 4.3.x release branch. This release addresses performance issues in the
+non-blocking connection pool implementation and also includes a number of performance improvements in the low level NIO
+based transport components.
+
+###### 24 April 2013 - HttpComponents HttpClient 4.2.5 (GA) released
+
+This is a maintenance release that addresses a number of issues reported since release 4.2.4 including a major bug that
+can lead to re-use of persistent connections in a inconsistent state.
+
+###### 11 April 2013 - HttpComponents HttpClient 4.3-beta1 released
+
+This is the first BETA release of HttpClient 4.3. The 4.3 branch enhances HttpClient in several key areas and includes
+several notable features and improvements: Support for Java 7 try-with-resources for resource management (connection
+release); fluent Builder classes for HttpEntity, HttpRequest and HttpClient instances, deprecation of preference and
+configuration API based on HttpParams interface in favor of constructor injection and plain configuration objects,
+reliance on object immutability instead of access synchronization for thread safety.
+
+This release also includes all fixes from the stable 4.2.x release branch.
+
+###### 11 April 2013 - HttpComponents HttpClient 4.2.4 (GA) released
+
+This is a bug fix release that addresses a number of issues reported since release 4.2.3.
+
+###### 25 March 2013 - HttpComponents HttpCore 4.3-beta1 released
+
+This is the first BETA release from the 4.3 release branch. The main theme of the 4.3 release series is streamlining of
+component configuration and deprecation of the old configuration API based on HttpParams in favor of constructor-based
+dependency injection and plain objects for configuration parameters.
+
+This release also includes performance optimizations intended to reduce TCP packet fragmentation when writing out HTTP
+messages both in blocking and non-blocking I/O modes, which should result in up to 20% higher throughput for short
+entity enclosing messages.
+
+###### 25 March 2013 - HttpComponents HttpCore 4.2.4 released
+
+This is a maintenance release that fixes a number of bugs found in NIO components since 4.2.3. We advise users of
+HttpCore NIO of all versions to upgrade.
+
+###### 21 January 2013 - HttpComponents HttpClient 4.3-alpha1 released
+
+This is the first ALPHA release of HttpClient 4.3. The 4.3 branch enhances HttpClient in several key areas and includes
+several notable features and improvements: Support for Java 7 try-with-resources for resource management (
+connection release); fluent Builder classes for HttpEntity, HttpRequest and HttpClient instances, deprecation of
+preference and configuration API based on HttpParams interface in favor of constructor injection and plain configuration
+objects, reliance on object immutability instead of access synchronization for thread safety.
+
+###### 15 January 2013 - HttpComponents HttpClient 4.2.3 (GA) released
+
+This is a bug fix release that addresses a number of issues reported since release 4.2.2. This release also includes a
+thoroughly reworked NTLM authentication engine which should result in a better compatibility with the newest Microsoft
+products.
+
+###### 08 Dec 2012 - Welcome new HttpComponents committer Karl Wright
+
+Karl Wright has been unanimously voted in as a new HttpComponents committer due to his invaluable help in supporting the
+internal NTLM engine and NTLM related authentication code.
+Karl is a committer on a number of ASF projects: Lucene, Lucene connectors, Incubator.
+
+Welcome on board, Karl!
+
+###### 30 November 2012 - HttpComponents HttpCore 4.3-alpha1 released
+
+This is the first release from the 4.3.x release branch. The main theme of the 4.3 release series is streamlining of
+component configuration and deprecation of the old configuration API based on HttpParams in favor of constructor-based
+dependency injection and plain objects for configuration parameters.
+
+###### 30 November 2012 - HttpComponents HttpCore 4.2.3 (GA) released
+
+HttpCore 4.2.3 is a maintenance release that fixes a number of bugs found since 4.2.2 including a major bug in the NIO
+module that can cause an infinite loop in SSL sessions under special circumstances when the remote peer terminates the
+session in the middle of SSL handshake. We advise users of HttpCore NIO of all versions to upgrade.
+
+###### 25 October 2012 - HttpComponents HttpClient 4.2.2 (GA) released
+
+HttpClient 4.2.2 is a bug fix release that addresses a number of issues reported since release 4.2.1. Users of
+HttpClient 4.2 are advised to upgrade.
+
+###### 29 September 2012 - HttpComponents HttpAsyncClient 4.0-beta3 released
+
+This is a maintenance release that picks up the latest bug fixes in the core components.
+
+###### 23 September 2012 - HttpComponents HttpCore 4.2.2 (GA) released
+
+This is a maintenance release that fixes a number of bugs and regressions found since 4.2.1 including a major bug in the
+NIO module causing incorrect handling of outgoing Content-Length delimited messages larger than 2GB. Users of HttpCore
+4.2 are advised to upgrade.
+
+###### 29 August 2012 - Welcome new HttpComponents committer William Speirs
+
+William Speirs, a long time contributor to the project, has been unanimously voted in as a new HttpComponents committer.
+William is already a committer on Apache Commons project.
+
+Welcome on board, William!
+
+###### 8 August 2011 - HttpComponents HttpAsyncClient 4.0-beta2 released
+
+This release fixes a number of non-critical issues found since release 4.0-beta1 and introduces basic support for
+HTTP/1.1 response caching. Please note that caching for streaming HTTP exchanges is currently not supported.
+
+###### 4 August 2012 - Welcome new HttpComponents committer Gary Gregory
+
+By 5 binding votes in favor Gary Gregory has been unanimously voted in as a new HttpComponents committer. Gary is
+already a committer on Apache Commons, Logging and Xalan projects.
+
+Welcome on board, Gary!
+
+###### 5 July 2012 - HttpComponents HttpClient 4.2.1 (GA) released
+
+HttpClient 4.2.1 is a bug fix release that addresses a number of issues reported since release 4.2. Users of HttpClient
+4.2 are advised to upgrade.
+
+###### 14 June 2012 - HttpComponents HttpCore 4.2.1 (GA) released
+
+HttpCore 4.2.1 is a patch release that fixes a number of non-critical bugs found since 4.2. Users of HttpCore 4.2 are
+advised to upgrade.
+
+###### 22 May 2012 - HttpComponents HttpClient 4.2 (GA) released
+
+This is the first stable (GA) release of HttpClient 4.2. The most notable enhancements included in this release are:
+
+- New facade API for HttpClient based on the concept of a fluent interface. The fluent API exposes only the most
+ fundamental functions of HttpClient and is intended for relatively simple use cases that do not require the full
+ flexibility of HttpClient. However, the fluent API almost fully relieves the users from having to deal with connection
+ management and resource deallocation.
+- Redesigned and rewritten connection management code.
+- Enhanced HTTP authentication API that enables HttpClient to handle more complex authentication scenarios. HttpClient
+ 4.2 is now capable of making use of multiple authentication challenges and retry authentication with a fall-back
+ scheme in case the primary one fails. This can be important for compatibility with Microsoft products that are often
+ configured to use SPNEGO/Kerberos as the preferred authentication scheme.
+
+###### 5 May 2012 - HttpComponents HttpCore 4.2 (GA) released
+
+This is the first stable (GA) release of HttpCore 4.2. The most notable features included in this release are connection
+pool components for blocking and non-blocking HTTP connections and new asynchronous client and server side protocol
+handlers.
+
+New protocol handling API used in conjunction with connection pooling components is expected to make development of
+asynchronous HTTP client agents and HTTP proxies easier and less error prone.
+
+Connection pool components are based on mature code migrated from HttpClient and HttpAsyncClient modules but have a
+slightly different API that makes a better use of Java standard concurrent primitives.
+
+###### 22 February 2012 - HttpComponents HttpAsyncClient 4.0-beta1 released
+
+This the first BETA release of HttpAsyncClient. This release completes the application programming interface and the
+feature set of HttpAsyncClient and upgrades to the latest versions of core and client components (HttpCore 4.2-beta1 and
+HttpClient 4.2-beta1). As of this release HttpAsyncClient is expected to be API stable.
+
+###### 10 February 2012 - HttpComponents HttpClient 4.2-beta1 released
+
+This is the first BETA release of HttpClient 4.2. This release completes development of several notable enhancements in
+HttpClient: new facade API, redesigned connection management code and new HTTP authentication API.
+
+###### 7 February 2012 - HttpComponents HttpClient 4.1.3 (GA) released
+
+HttpClient 4.1.3 is a bug fix release that addresses a number of non-critical issues found since 4.1.2 primarily in the
+HTTP caching module.
+
+###### 1 February 2012 - HttpComponents HttpCore 4.2-beta1 released
+
+This is the first BETA release of HttpCore 4.2. This release ships with an improved asynchronous protocol handling API
+and new non-blocking client and server HTTP protocol handler implementations. New API is expected to be more flexible
+especially for writing HTTP proxy or gateway type of services. Upstream projects are encouraged to evaluate the new API
+and give feedback.
+
+###### 23 December 2011 - HttpComponents HttpCore 4.1.4 (GA) released
+
+HttpCore 4.1.4 is a patch release that fixes a number of bugs found since 4.1.3. It is also likely to be the last
+release in the 4.1.x branch.
+
+###### 3 November 2011 - HttpComponents HttpClient 4.2-alpha1 released
+
+This is the first ALPHA release of HttpClient 4.2. The 4.2 branch enhances HttpClient in several key areas and includes
+several notable features and improvements: new facade API, redesigned connection management code and new HTTP
+authentication API.
+
+###### 29 September 2011 - HttpComponents HttpAsyncClient 4.0-alpha3 released
+
+This is the third ALPHA release of HttpAsyncClient 4.0. This release largely completes the application programming
+interface and feature set of HttpAsyncClient. While the API may still change in the course of the ALPHA development
+phase, this is expected to be the last round of major API changes and the API is expected to be reasonably stable as of
+this release.
+
+###### 23 September 2011 - HttpComponents HttpCore 4.2-alpha2 released
+
+This is the second ALPHA release of HttpCore 4.2. This release comes with completely redesigned and rewritten
+asynchronous protocol handlers. New protocol handling API used in conjunction with connection pooling components
+introduced in the previous ALPHA release is expected to make development of asynchronous HTTP client agents and HTTP
+proxies easier and less error prone.
+
+###### 19 August 2011 - HttpComponents HttpCore 4.2-alpha1 released
+
+This is the first ALPHA release of the 4.2 development branch. The most notable feature included in this release is
+support for connection pools of blocking and non-blocking HTTP connections. Connection pool components are based on
+mature code migrated from HttpClient and HttpAsyncClient modules but have a slightly different API that makes a better
+use of Java standard concurrent primitives. Support for connection pools in HttpCore is expected to make development of
+client and proxy HTTP services easier and less error prone.
+
+###### 7 August 2011 - HttpComponents HttpClient 4.1.2 (GA) released
+
+HttpClient 4.1.2 is a bug fix release that addresses a number of non-critical issues reported since release 4.1.1.
+
+###### 31 July 2011 - HttpComponents HttpCore 4.1.3 (GA) released
+
+HttpCore 4.1.3 is a patch release that fixes a critical regression in the non-blocking SSL I/O session code introduced
+in the 4.1.2 release.
+
+###### 18 July 2011 - HttpComponents HttpCore 4.1.2 (GA) released
+
+HttpCore 4.1.2 is a patch release that fixes a number of non-critical issues found since release 4.1.1.
+
+###### 24 May 2011 - HttpComponents HttpAsyncClient 4.0-alpha2 released
+
+The second ALPHA release of HttpAsyncClient 4.0 comes with a number of important improvements and enhancements. As of
+this version HttpAsyncClient fully supports HTTP state management
+(cookies) and HTTP authentication (basic, digest, NTLM, spnego/kerberos). Connection management classes have been
+thoroughly reworked and improved. This version also improves support for zero copy file upload / download operations.
+
+###### 20 May 2011 - HttpComponents HttpCore 4.1.1 (GA) released
+
+HttpCore 4.1.1 is a patch release that fixes a number of non-critical issues found since release 4.1.
+
+This release marks the end of support for Java 1.3. As of release 4.2 HttpCore will require Java 1.5 for all its
+components.
+
+###### 20 March 2011 - HttpComponents HttpClient 4.1.1 (GA) released
+
+HttpClient 4.1.1 is a bug fix release that addresses a number of issues reported since release 4.1, including one
+critical security issue.
+
+###### 23 January 2011 - HttpComponents HttpClient 4.1 (GA) released
+
+The HttpClient 4.1 release builds upon the stable foundation laid by HttpClient 4.0 and adds several functional
+improvements and popular features.
+
+- Response caching conditionally compliant with HTTP/1.1 specification (full compliance with MUST requirements, partial
+ compliance with SHOULD requirements)
+- Full support for NTLMv1, NTLMv2, and NTLM2 Session authentication. The NTLM protocol code was kindly contributed by
+ the Lucene Connector Framework project.
+- Support for SPNEGO/Kerberos authentication.
+- Persistence of authentication data between request executions within the same execution context.
+- Support for preemptive authentication for BASIC and DIGEST schemes.
+- Support for transparent content encoding. Please note transparent content encoding is not enabled per default in order
+ to avoid conflicts with already existing custom content encoding solutions.
+- Mechanism to bypass the standard certificate trust verification (useful when dealing with self-signed certificates).
+- Simplified configuration for connection managers.
+- Transparent support for host multihoming.
+
+###### 18 January 2011 - HttpComponents HttpAsyncClient 4.0-alpha1 released
+
+This is the first public release of HttpAsyncClient. The HttpAsyncClient 4.0 API is considered very experimental and is
+expected to change in the course of the ALPHA development phase. This release is primarily intended for early adopters
+who may be interested in contributing to the project and in helping shape the new API.
+
+###### 21 November 2010 - HttpComponents HttpClient 4.1-beta1 released
+
+This release finalizes the 4.1 API and brings a number of major improvements to the HTTP caching module. This release
+also adds full support for NTLMv1, NTLMv2, and NTLM2 Session authentication schemes. The NTLM protocol code was kindly
+contributed by the Lucene Connector Framework project.
+
+###### 19 November 2010 - HttpComponents HttpCore 4.1 (GA) released
+
+This is the first stable release of HttpCore 4.1. This release provides a compatibility mode with JREs that have a
+naive (broken) implementation of SelectionKey API and also improves compatibility with the Google Android platform.
+There has also been a number of performance related improvements and bug fixes in both blocking and non-blocking
+components.
+
+###### 26 October 2010 - Welcome new HttpComponents committer Jonathan Moore
+
+By 4 binding votes in favor and none against Jonathan Moore has been voted in as a new HttpComponents committer.
+Jonathan has made major contributions to the new HttpClient caching module.
+
+Welcome on board, Jonathan!
+
+###### 19 September 2010 - HttpComponents HttpClient 4.0.3 (GA) released
+
+This is an emergency release fixing a critical regression in the SSL connection management code.
+
+###### 9 September 2010 - HttpComponents HttpClient 4.0.2 (GA) released
+
+This is a maintenance release that fixes a number of bugs found since 4.0.1. This is likely to be the last release in
+the 4.0.x branch.
+
+###### 30 August 2010 - HttpComponents HttpCore 4.1-beta2 released
+
+This release addresses fixes a number of non-critical bugs. It is likely to be the last BETA release in the 4.1 branch.
+
+###### 19 May 2010 - HttpComponents HttpClient 4.1-alpha2 released
+
+This release fixes a number of non-severe bugs discovered since the last release and introduces support for two
+frequently requested features:
+
+- HTTP/1.1 response caching
+- transparent support for host multihoming
+- a mechanism to bypass the standard certificate trust verification (useful when dealing with self-signed certificates)
+
+###### 3 April 2010 - HttpComponents HttpCore 4.1-beta1 released
+
+This release finalizes the API introduced in the 4.1 development branch. It also fixes a number of bugs discovered since
+the previous release and delivers a number of performance optimizations in the blocking HTTP transport components. The
+blocking HTTP transport is expected to be 5% to 10% faster compared to previous releases.
+
+###### 11 December 2009 - HttpComponents HttpClient 4.1-alpha1 released
+
+This release builds on the stable 4.0 release and adds several functionality improvements and new features.
+
+- Simplified configuration of connection managers.
+- Persistence of authentication data between request executions within the same execution context.
+- Support for SPNEGO/Kerberos authentication scheme
+- Support for transparent content encoding. Please note transparent content encoding is not enabled per default in order
+ to avoid conflicts with already existing custom content encoding solutions.
+
+###### 11 December 2009 - HttpComponents HttpClient 4.0.1 (GA) released
+
+This is a bug fix release that addresses a number of issues discovered since the previous stable release. None of the
+fixed bugs is considered critical. Most notably this release eliminates dependency on JCIP annotations.
+
+This release is also expected to improve performance by 5 to 10% due to elimination of unnecessary Log object lookups by
+short-lived components.
+
+###### 12 September 2009 - HttpComponents HttpCore 4.1-alpha1 released
+
+This is the first public release from the 4.1 branch of HttpCore. This release adds a number of new features, most
+notable being introduction of compatibility mode with IBM JREs and other JREs with naive (broken) implementation of
+SelectionKey API.
+
+###### 14 August 2009 - HttpComponents HttpClient 4.0 (GA) released
+
+This the first stable (GA) release in the 4.x code line. This release completes the rewrite of HttpClient and delivers a
+complete API documentation and fixes a few minor bugs reported since the previous release.
+
+###### 22 June 2009 - HttpComponents HttpCore 4.0.1 (GA) released
+
+This is a patch release addressing a number of issues discovered since the 4.0 release.
+
+###### 26 February 2009 - HttpComponents HttpCore 4.0 (GA) released
+
+This the first stable (GA) release in the 4.x code line. This release delivers complete API documentation and fixes a
+few minor bugs reported since the previous release.
+
+###### 20 December 2008 - HttpComponents HttpClient 4.0-beta2 released
+
+The second BETA of HttpComponents HttpClient addresses a number of issues discovered since the previous release.
+
+The only significant new feature is an addition of an OSGi compliant bundle combining HttpClient and HttpMime jars.
+
+All upstream projects are strongly encouraged to upgrade.
+
+###### 19 October 2008 - HttpComponents HttpCore 4.0-beta3 released
+
+The third BETA version of HttpComponents Core addresses a number of issues discovered since the previous release.
+
+The only significant new feature is an addition of an OSGi compliant bundle combining HttpCore and HttpCore NIO jars.
+
+###### 12 September 2008 - HttpClient is one of the best open source development tools
+
+HttpClient is among the 60 winners of
+InfoWorlds ["Best of Open Source Software Awards 2008"](http://www.infoworld.com/article/08/08/04/32TC-bossies-2008_1.html)
+.
+
+HttpClient was selected as one of
+the [best open source development tools](http://www.infoworld.com/slideshow/2008/08/166-best_of_open_so-4.html).
+
+###### 29 August 2008 - HttpComponents HttpClient 4.0-beta1 released
+
+The first BETA brings yet another round of API enhancements and improvements in the area of connection management. Among
+the most notable ones is the capability to handle stateful connections such as persistent NTLM connections and private
+key authenticated SSL connections.
+
+This is the first API stable release of HttpClient 4.0. All further releases in the 4.0 code line will maintain API
+compatibility with this release.
+
+###### 22 June 2008 - HttpComponents HttpCore 4.0-beta2 released
+
+The second BETA version of HttpComponents Core added a number of improvements to the NIO components, most notable being
+improved asynchronous client side and server side protocol handlers.
+
+###### 09 May 2008 - HttpComponents HttpClient 4.0-alpha4 released
+
+The fourth ALPHA marks the completion of the overhaul of the connection management code in HttpClient. All known
+shortcomings of the old HttpClient 3.x connection management API have been addressed.
+
+###### 03 May 2008 - Welcome new HttpComponents committer Sam Berlin
+
+By 6 binding votes in favor and none against Sam Berlin has been voted in as a new HttpComponents committer. Sam made
+several valuable contributions to both core and client components in the course of the past several months.
+
+Welcome on board, Sam!
+
+###### 26 February 2008 - HttpComponents HttpClient 4.0-alpha3 released
+
+The third ALPHA release brings another round of API refinements and improvements in functionality. As of this release
+HttpClient requires Java 5 compatible runtime environment and takes full advantage of generics and new concurrency
+primitives.
+
+This release also introduces new default cookie policy that selects a cookie specification depending on the format of
+cookies sent by the target host. It is no longer necessary to know beforehand what kind of HTTP cookie support the
+target host provides. HttpClient is now able to pick up either a lenient or a strict cookie policy depending on the
+compliance level of the target host.
+
+Another notable improvement is a completely reworked support for multipart entities based on Apache mime4j library.
+
+###### 24 January 2008 - HttpComponents HttpCore 4.0-beta1 released
+
+The first BETA version of HttpComponents Core has been released. This release can be considered a major milestone, as it
+marks the end of API instability in HttpCore. As of this release the API compatibility between minor releases in 4.x
+codeline will be maintained.
+
+This release includes several major improvements such as enhanced HTTP message parsing API and optimized parser
+implementations, Java 5.0 compatibility for HttpCore NIO extensions.
+
+The focus of the development efforts will be gradually shifting towards providing better test coverage, documentation
+and performance optimizations.
+
+###### 15 November 2007 - HttpComponents becomes TLP
+
+The ASF board had approved HttpComponents 'graduation' from Jakarta to a TLP of its own.
+
+We are now Apache HttpComponents Project!
+
+###### 7 November 2007 - HttpComponents HttpClient 4.0-alpha2 released
+
+The second ALPHA release is another important milestone in the redesign of HttpClient. The release includes a number of
+improvements since ALPHA1, among which are improved connection pooling, support for proxy chains, redesigned HTTP state
+and authentication credentials management API, improved RFC 2965 cookie specification.
+
+###### 9 October 2007 - HttpComponents HttpCore 4.0-alpha6 released
+
+The sixth ALPHA version of HttpComponents Core has been released. This release sports an improved message parsing and
+formatting API in the base module and lots of incremental improvements and bug fixes in the NIO and NIOSSL modules.
+Based on the improved API, it is now possible to send and receive SIP messages with HttpComponents Core.
+
+###### 20 July 2007 - HttpComponents HttpClient 4.0-alpha1 released
+
+This release represents a complete, ground-up redesign and almost a complete rewrite of the old HttpClient 3.x codeline.
+This release finally addresses several design flaws that existed since the 1.0 release and could not be fixed without a
+major code overhaul and breaking API compatibility.
+
+Notable changes and enhancements:
+
+- Redesign of the HttpClient internals addressing all known major architectural shortcomings of the 3.x codeline
+- Cleaner, more flexible and expressive API
+- Better performance and smaller memory footprint due to a more efficient HTTP transport based on HttpCore. HttpClient
+ 4.0 is expected to be 10% to 25% faster than HttpClient 3.x codeline
+- More modular structure
+- Pluggable redirect and authentication handlers
+- Support for protocol incerceptors
+- Improved connection management
+- Improved support for sending requests via a proxy or a chain of proxies
+- Improved handling redirects of entity enclosing requests
+- More flexible SSL context customization
+- Reduced intermediate garbage in the process of generating HTTP requests and parsing HTTP responses
+
+###### 4 July 2007 - HttpComponents HttpCore 4.0-alpha5 released
+
+The fifth ALPHA version of HttpComponents Core has been released. This release delivers a number of incremental
+improvements across the board in all modules and adds several performance oriented features such as ability to transfer
+data directly between a file and a socket NIO channels.
+
+###### 30 March 2007 - HttpComponents HttpCore 4.0-alpha4 released
+
+The fourth ALPHA version fixes a number of bugs and adds a number of improvements to HttpCore base and the HttpCore NIO
+extensions. This release also introduces NIOSSL extensions that can be used to extend HttpCore non-blocking transport
+components with the ability to transparently encrypt data in transit using SSL/TLS.
+
+###### 6 December 2006 - HttpComponents HttpCore 4.0-alpha3 released
+
+The third ALPHA version of HttpCore has been released. The ALPHA3 release includes a number of API optimizations and
+improvements and introduces a set of NIO extensions to the HttpCore API. NIO extensions can be used to build HTTP
+services intended to handle thousands of simultaneous connections with a small number of I/O threads.
+
+###### 9 June 2006 - HttpComponents HttpCore 4.0-alpha2 released
+
+The second ALPHA version of HttpCore has been released, which addresses a number of non-critical problems found in the
+previous release. The upstream projects are strongly encouraged use this release as a dependency while HttpCore
+undergoes another round of reviews and optimization in the SVN trunk.
+
+###### 12 May 2006 - HttpClient issue tracking migrated to Jira
+
+HttpClient issue tracking has migrated from Bugzilla to Jira. Please use
+[this project](http://issues.apache.org/jira/browse/HTTPCLIENT) in Jira to report new issues against HttpClient and
+search for reported ones. All existing issue reports can be accessed in Jira by their original Bugzilla bug id.
+
+###### 29 April 2006 - New Project Logo
+
+HttpComponents project now has a brand new logo kindly contributed by Regula Wernli.
+
+Many thanks, Regula!
+
+###### 23 April 2006 - HttpComponents HttpCore 4.0-alpha1 released
+
+This is the first ALPHA release of HttpCore intended for API review and use in experimental projects. The HttpCore API
+is still deemed unstable and it can still undergo significant changes based on the feedback from early adopters.
+
+###### 12 February 2006 - Welcome new HttpComponents committer Roland Weber
+
+By 5 binding votes in favor and none against Roland Weber has been voted in as a new HttpComponents committer. Roland
+has been an invaluable contributor to the Jakarta Commons HttpClient project for many years and he is the very first
+committer to join the Jakarta HttpComponents project.
+
+Welcome, Roland
+
+###### 31 October 2005 - Jakarta HttpClient becomes Jakarta HttpComponents
+
+By the count 15 votes in favor, Jakarta HttpClient as been renamed as Jakarta HttpComponents. The Jakarta PMC has
+approved the new project charter and the new project scope.
+
+###### 16 April 2004 - Welcome Jakarta HttpClient!
+
+By the count 26 votes in favor, none against, Jakarta Commons HttpClient as been promoted to the Jakarta sub-project
+level
diff --git a/src/site/markdown/status.md b/src/site/markdown/status.md
new file mode 100644
index 0000000..63a3d92
--- /dev/null
+++ b/src/site/markdown/status.md
@@ -0,0 +1,84 @@
+<!--
+ Licensed to the Apache Software Foundation (ASF) under one
+ or more contributor license agreements. See the NOTICE file
+ distributed with this work for additional information
+ regarding copyright ownership. The ASF licenses this file
+ to you under the Apache License, Version 2.0 (the
+ "License"); you may not use this file except in compliance
+ with the License. You may obtain a copy of the License at
+
+ http://www.apache.org/licenses/LICENSE-2.0
+
+ Unless required by applicable law or agreed to in writing,
+ software distributed under the License is distributed on an
+ "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+ KIND, either express or implied. See the License for the
+ specific language governing permissions and limitations
+ under the License.
+-->
+
+HttpComponents Project Status
+=============================
+
+HttpComponents HttpCore 5.1.x
+-----------------------------
+
+HttpCore 5.1.x branch is the current feature development branch. The 5.x release series is expected to provide
+conditional conformance to RFC 3986 as well as a number of incremental functional enhancements and performance
+improvements.
+
+This is likely to be the last release series with Java 1.7 support.
+
+HttpComponents HttpCore 5.1.x
+-----------------------------
+
+HttpCore 5.1.x branch is the current feature development branch. The 5.x release series is expected to provide
+conditional conformance to RFC 3986 as well as a number of incremental functional enhancements and performance
+improvements.
+
+This is likely to be the last release series with Java 1.7 support.
+
+HttpComponents HttpCore 5.0.x
+-----------------------------
+
+HttpCore 5.0.x branch is considered stable and production ready. It is being actively maintained and supported. The 5.x
+release series provides comprehensive support for HTTP/1.1 and HTTP/2 protocol and full conformance with mandatory
+requirements of RFC 7230, RFC 7231, RFC 7540 and RFC 7541
+
+HttpComponents HttpClient 5.0.x
+-------------------------------
+
+HttpClient 5.0.x branch is considered stable and production ready. It is being actively maintained and supported. The
+5.x release series provides comprehensive support for HTTP/1.1 and HTTP/2 protocol and full conformance with mandatory
+requirements of RFC 7230, RFC 7231, RFC 7540 and RFC 7541
+
+HttpComponents HttpCore 4.4.x
+-----------------------------
+
+HttpCore 4.4.x branch is considered stable and production ready. While being actively maintained and supported, the 4.x
+release series will be receiving fixes for major defects and security issues only.
+
+Users of HttpCore 4.x are strongly encouraged to migrate to HttpCore 5.x
+
+HttpComponents HttpClient 4.5.x
+-------------------------------
+
+HttpClient 4.5.x branch is considered stable and production ready. While being actively maintained and supported, the
+4.x release series will be receiving fixes for major defects and security issues only.
+
+HttpComponents HttpAsyncClient 4.1.x
+------------------------------------
+
+HttpAsyncClient 4.1.x branch is considered stable and production ready. While being actively maintained and supported,
+the 4.x release series will be receiving fixes for major defects and security issues only.
+
+Users of HttpAsyncClient 4.x are strongly encouraged to migrate to HttpClient 5.x
+
+Commons HttpClient 3.1.x
+------------------------
+
+The 3.1 branch of Commons HttpClient is at the end of life. No more public releases are expected.
+
+
+
+
diff --git a/src/site/site.xml b/src/site/site.xml
index 0216516..a7c3830 100644
--- a/src/site/site.xml
+++ b/src/site/site.xml
@@ -67,7 +67,6 @@ under the License.
<menu name="Overview">
<item name="About" href="index.html"/>
<item name="News" href="news.html"/>
- <item name="Powered by" href="poweredby.html"/>
<item name="Get Involved" href="get-involved.html"/>
</menu>
<menu name="Components">