[ANNOUNCEMENT] HttpComponents Client 5.0 Alpha1 Released

[Oleg Kalnichevski]

The Apache HttpComponents project is pleased to announce 5.0 Alpha1
release of HttpComponents HttpClient.

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.

Notable changes and features included in the 5.0 series are:

* Improved conformance to requirements and recommendations of the latest
HTTP/1.1 protocol specification (RFC 7230, RFC 7231, RFC 7235)

* Package name space changed to 'org.apache.hc.client5'

* Maven group id changed to 'org.apache.httpcomponents.client5'

* By default the maximum connections per route limit is set to 5

* By default connection request timeout and connect timeout are set to 3
minutes.

HttpClient 5.0 releases can be co-located with earlier versions, meaning
you can have both 5.x and  4.x on the classpath without experiencing jar
hell.

Please note that as of 5.0 HttpClient requires Java 1.7 or newer.

Please note that at this point we consider 5.0 APIs experimental and
unstable and expect them to change in the coming releases without
providing a migration path.

Download - 
Release notes -

HttpComponents site - 

About HttpComponents HttpClient

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.

Although the java.net package provides basic functionality for accessing
resources via HTTP, it doesn't provide the full flexibility or
functionality needed by many applications. HttpClient seeks to fill this
void by providing an efficient, up-to-date, and feature-rich package
implementing the client side of the most recent HTTP standards and
recommendations.

Designed for extension while providing robust support for the base HTTP
protocol, HttpClient may be of interest to anyone building HTTP-aware
client applications such as web browsers, web service clients, or
systems that leverage or extend the HTTP protocol for distributed
communication.



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

A minor struggle with multipart/mixed

[Benson Margulies]

This is with version 4.4.1, so perhaps it's old news.

I'm trying to use the Mime library to set up a multipart/mixed entity.

I need Content-Disposition inline, not form-data. To get it, I have to
explicitly build the FormBodyParts, as the convenient methods on the
multipart entity builder all end up with form-data.

Would anyone be interested in a patch to add more methods to
MultipartEntityBuilder to make this easier?

I also ran into the fact that ContentType.APPLICATION_JSON adds
;charset=utf-8, which I'm assured is wrong for json, which is only
ever supposed to be utf-8 on the wire.

Could we add a new constant for, somehow, 'plain' APPLICATION_JSON?

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

Re: A minor struggle with multipart/mixed

[Gary Gregory]

Hi Benson,

I think that if we add anything to the 4.x line, it will be for the
upcoming 4.5.2, so you'll want to migrate to 4.5.1 and propose a patch
there.

AFAIK there are no plans for another 4.4.x release.

Gary

On Thu, Jan 28, 2016 at 6:08 PM, Benson Margulies 
wrote:

> This is with version 4.4.1, so perhaps it's old news.
>
> I'm trying to use the Mime library to set up a multipart/mixed entity.
>
> I need Content-Disposition inline, not form-data. To get it, I have to
> explicitly build the FormBodyParts, as the convenient methods on the
> multipart entity builder all end up with form-data.
>
> Would anyone be interested in a patch to add more methods to
> MultipartEntityBuilder to make this easier?
>
> I also ran into the fact that ContentType.APPLICATION_JSON adds
> ;charset=utf-8, which I'm assured is wrong for json, which is only
> ever supposed to be utf-8 on the wire.
>
> Could we add a new constant for, somehow, 'plain' APPLICATION_JSON?
>
> -
> To unsubscribe, e-mail: httpclient-users-unsubscr...@hc.apache.org
> For additional commands, e-mail: httpclient-users-h...@hc.apache.org
>
>


-- 
E-Mail: garydgreg...@gmail.com | ggreg...@apache.org
Java Persistence with Hibernate, Second Edition

JUnit in Action, Second Edition 
Spring Batch in Action 
Blog: http://garygregory.wordpress.com
Home: http://garygregory.com/
Tweet! http://twitter.com/GaryGregory