Re: Draft board report for May 2014
On Wed, 2014-05-07 at 23:38 +0530, Asankha C. Perera wrote: Hi All Its again the time for our report to the board. Could you review the draft I've put together, and update anything I've missed. The deadline is the 14th of May for submission, so I appreciate if you could review before the 12th http://wiki.apache.org/HttpComponents/BoardReportDraft thanks asankha Hi Asankha Sorry for a belated response. There was an extended outage of ASF email services and I received your email only yesterday. I added a short description of that HttpClient for Android is, just in case. +1 Oleg - To unsubscribe, e-mail: dev-unsubscr...@hc.apache.org For additional commands, e-mail: dev-h...@hc.apache.org
[Httpcomponents Wiki] Update of BoardReportDraft by OlegKalnichevski
Dear Wiki user, You have subscribed to a wiki page or wiki category on Httpcomponents Wiki for change notification. The BoardReportDraft page has been changed by OlegKalnichevski: https://wiki.apache.org/HttpComponents/BoardReportDraft?action=diffrev1=36rev2=37 Overall the project remains active. == Releases == - HttpComponents 4.3.2 GA was released on the 17th of February 2014 + HttpCore 4.3.2 GA was released on the 17th of February 2014 HttpAsyncClient 4.0.1 GA was released on the 24th of February 2014 HttpClient 4.3.3 GA was released on the 27th of February 2014 - HttpComponents Client for Android 4.3.3 was released on 20th of March 2014 + HttpClient for Android 4.3.3 was released on 20th of March 2014 + + HttpClient for Android is a port of Apache HttpClient, which can be deployed on Google Android in parallel to the outdated version shipped with the platform while remaining partially API compatible with Apache HttpClient 4.3. == Community == - To unsubscribe, e-mail: dev-unsubscr...@hc.apache.org For additional commands, e-mail: dev-h...@hc.apache.org
[jira] [Created] (HTTPCLIENT-1507) Quick start comments do not correspond to user guide
Michael Osipov created HTTPCLIENT-1507:
--
Summary: Quick start comments do not correspond to user guide
Key: HTTPCLIENT-1507
URL: https://issues.apache.org/jira/browse/HTTPCLIENT-1507
Project: HttpComponents HttpClient
Issue Type: Improvement
Components: Documentation
Affects Versions: 4.3.3
Reporter: Michael Osipov
[Quick start|http://hc.apache.org/httpcomponents-client-ga/quickstart.html]
says:
{quote}
// The underlying HTTP connection is still held by the response object
// to allow the response content to be streamed directly from the network
socket.
// In order to ensure correct deallocation of system resources
// the user MUST either fully consume the response content or abort request
// execution by calling CloseableHttpResponse#close().
{quote}
but the [user
guide|http://hc.apache.org/httpcomponents-client-4.3.x/tutorial/html/fundamentals.html#d5e145]
says:
{quote}
The difference between closing the content stream and closing the response is
that the former will attempt to keep the underlying connection alive by
consuming the entity content while the latter immediately shuts down and
discards the connection.
{quote}
This is a contradiction. The code which follows in the quick start is correct
but not the comment. Even if I consume the response content the underlying
connection is still help open.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
-
To unsubscribe, e-mail: dev-unsubscr...@hc.apache.org
For additional commands, e-mail: dev-h...@hc.apache.org
[jira] [Commented] (HTTPASYNC-74) IllegalStateException when sharing the connection manager amongst HttpAsyncClient instances
[ https://issues.apache.org/jira/browse/HTTPASYNC-74?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13995001#comment-13995001 ] Oleg Kalnichevski commented on HTTPASYNC-74: No good reason. Corrected in SVN trunk. Please review. Oleg IllegalStateException when sharing the connection manager amongst HttpAsyncClient instances --- Key: HTTPASYNC-74 URL: https://issues.apache.org/jira/browse/HTTPASYNC-74 Project: HttpComponents HttpAsyncClient Issue Type: Bug Affects Versions: 4.0.1 Environment: JDK 1.7 Reporter: Jose Dillet Fix For: 4.1-alpha1 Attachments: SharedHttpAsyncClient.java When several HttpAsyncClient instances share the same connection manager, IllegalStateException is thrown: 15:23:10 ERROR - I/O reactor terminated abnormally java.lang.IllegalStateException: Illegal state ACTIVE at org.apache.http.util.Asserts.check(Asserts.java:40) at org.apache.http.impl.nio.reactor.AbstractMultiworkerIOReactor.execute(AbstractMultiworkerIOReactor.java:313) at org.apache.http.impl.nio.conn.PoolingNHttpClientConnectionManager.execute(PoolingNHttpClientConnectionManager.java:189) at org.apache.http.impl.nio.client.CloseableHttpAsyncClientBase.doExecute(CloseableHttpAsyncClientBase.java:67) at org.apache.http.impl.nio.client.CloseableHttpAsyncClientBase.access$000(CloseableHttpAsyncClientBase.java:38) at org.apache.http.impl.nio.client.CloseableHttpAsyncClientBase$1.run(CloseableHttpAsyncClientBase.java:57) at java.lang.Thread.run(Thread.java:744) GET http://www.apache.org/ HTTP/1.1-HTTP/1.1 200 OK Exception in thread main java.lang.IllegalStateException: Request cannot be executed; I/O reactor status: STOPPED at org.apache.http.util.Asserts.check(Asserts.java:40) at org.apache.http.impl.nio.client.InternalHttpAsyncClient.execute(InternalHttpAsyncClient.java:112) at org.apache.http.impl.nio.client.CloseableHttpAsyncClient.execute(CloseableHttpAsyncClient.java:72) at org.apache.http.impl.nio.client.CloseableHttpAsyncClient.execute(CloseableHttpAsyncClient.java:102) at org.apache.http.impl.nio.client.CloseableHttpAsyncClient.execute(CloseableHttpAsyncClient.java:87) at org.apache.http.examples.nio.client.SharedHttpAsyncClient2.makeRequest(SharedHttpAsyncClient2.java:51) at org.apache.http.examples.nio.client.SharedHttpAsyncClient2.main(SharedHttpAsyncClient2.java:40) -- This message was sent by Atlassian JIRA (v6.2#6252) - To unsubscribe, e-mail: dev-unsubscr...@hc.apache.org For additional commands, e-mail: dev-h...@hc.apache.org
[jira] [Resolved] (HTTPCLIENT-1505) Add a MultipartEntityReader
[ https://issues.apache.org/jira/browse/HTTPCLIENT-1505?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Oleg Kalnichevski resolved HTTPCLIENT-1505. --- Resolution: Won't Fix Michael, It took several years and *a lot* of hard work to develop a reasonable MIME parser in Apache Mime4j [1] I see no reason of what so ever for duplicating these efforts in HC. Oleg [1] http://james.apache.org/mime4j/index.html Add a MultipartEntityReader --- Key: HTTPCLIENT-1505 URL: https://issues.apache.org/jira/browse/HTTPCLIENT-1505 Project: HttpComponents HttpClient Issue Type: New Feature Components: HttpMime Affects Versions: 4.3.3 Reporter: Michael Osipov Currently, HttpMime allows to build multipart entities but one cannot parse them from a response. One has to rely on a third-party lib. It would be handy if such components would be avaiable in this package. -- This message was sent by Atlassian JIRA (v6.2#6252) - To unsubscribe, e-mail: dev-unsubscr...@hc.apache.org For additional commands, e-mail: dev-h...@hc.apache.org
Caching responses to HEAD requests in httpclient-cache
Hi all, We're using HTTP Client 4.x with httpclient-cache. Our system needs to retrieve some metadata over HTTP that is returned in a Header Field, so it only needs to make a HEAD request. However, as it stands httpclient-cache does not cache the responses to HEAD requests. While the HTTP spec doesn't (by my reading) take a positive position on whether or not you can cache responses to HEAD requests, there doesn't seem any particular reason why they shouldn't be cached, with the obvious proviso that a GET request to a resource which currently only has a cached header must result in a request to origin, and that PUT, POST DELETE requests should all invalidate the cache for that resource as usual. We're considering extending httpclient-cache to make this possible, but we don't want to lock ourselves out of upgrading forever. If we were to do so and offer to contribute it back to the project would you be interested? Regards, Rob -- -- This email was sent by a company owned by Pearson plc, registered office at 80 Strand, London WC2R 0RL. Registered in England and Wales with company number 53723.
[jira] [Commented] (HTTPCLIENT-1505) Add a MultipartEntityReader
[ https://issues.apache.org/jira/browse/HTTPCLIENT-1505?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13995101#comment-13995101 ] Michael Osipov commented on HTTPCLIENT-1505: Wow, thanks. That should work actually. I will look into it. Add a MultipartEntityReader --- Key: HTTPCLIENT-1505 URL: https://issues.apache.org/jira/browse/HTTPCLIENT-1505 Project: HttpComponents HttpClient Issue Type: New Feature Components: HttpMime Affects Versions: 4.3.3 Reporter: Michael Osipov Currently, HttpMime allows to build multipart entities but one cannot parse them from a response. One has to rely on a third-party lib. It would be handy if such components would be avaiable in this package. -- This message was sent by Atlassian JIRA (v6.2#6252) - To unsubscribe, e-mail: dev-unsubscr...@hc.apache.org For additional commands, e-mail: dev-h...@hc.apache.org
[jira] [Updated] (HTTPCLIENT-1508) Default user agent should reflect the Java version used and not compiled
[
https://issues.apache.org/jira/browse/HTTPCLIENT-1508?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Oleg Kalnichevski updated HTTPCLIENT-1508:
--
Fix Version/s: 4.4 Alpha1
Default user agent should reflect the Java version used and not compiled
Key: HTTPCLIENT-1508
URL: https://issues.apache.org/jira/browse/HTTPCLIENT-1508
Project: HttpComponents HttpClient
Issue Type: Improvement
Components: HttpClient
Affects Versions: 4.3.3
Reporter: Michael Osipov
Fix For: 4.4 Alpha1
Currently, the dafault user agent looks like this:
{noformat}
DEFAULT_USER_AGENT = Apache-HttpClient/ + release + (java 1.5)
{noformat}
This indicates that Java 1.5 is used but this is the compile target of HTTP
Client.
A better user agent would be:
{noformat}
DEFAULT_USER_AGENT = Apache-HttpClient/ + release + (Java + javaVersion
)
{noformat}
where {{javaVersion}} is the version where the client is currently running.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
-
To unsubscribe, e-mail: dev-unsubscr...@hc.apache.org
For additional commands, e-mail: dev-h...@hc.apache.org
[jira] [Comment Edited] (HTTPCLIENT-1505) Add a MultipartEntityReader
[ https://issues.apache.org/jira/browse/HTTPCLIENT-1505?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13995101#comment-13995101 ] Michael Osipov edited comment on HTTPCLIENT-1505 at 5/12/14 2:29 PM: - Wow, thanks. That should work actually. I will look into it. After a look, it is requires some certain amount of code. While Commons Upload seems easier to use, it is coupled to tight to the servlet request. was (Author: michael-o): Wow, thanks. That should work actually. I will look into it. Add a MultipartEntityReader --- Key: HTTPCLIENT-1505 URL: https://issues.apache.org/jira/browse/HTTPCLIENT-1505 Project: HttpComponents HttpClient Issue Type: New Feature Components: HttpMime Affects Versions: 4.3.3 Reporter: Michael Osipov Currently, HttpMime allows to build multipart entities but one cannot parse them from a response. One has to rely on a third-party lib. It would be handy if such components would be avaiable in this package. -- This message was sent by Atlassian JIRA (v6.2#6252) - To unsubscribe, e-mail: dev-unsubscr...@hc.apache.org For additional commands, e-mail: dev-h...@hc.apache.org
[jira] [Commented] (HTTPCLIENT-1507) Quick start comments do not correspond to user guide
[
https://issues.apache.org/jira/browse/HTTPCLIENT-1507?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13995006#comment-13995006
]
Oleg Kalnichevski commented on HTTPCLIENT-1507:
---
I am sorry, Michael, but I fail to see a contradiction here. How would you
rephrase these statements?
Oleg
Quick start comments do not correspond to user guide
Key: HTTPCLIENT-1507
URL: https://issues.apache.org/jira/browse/HTTPCLIENT-1507
Project: HttpComponents HttpClient
Issue Type: Improvement
Components: Documentation
Affects Versions: 4.3.3
Reporter: Michael Osipov
[Quick start|http://hc.apache.org/httpcomponents-client-ga/quickstart.html]
says:
{quote}
// The underlying HTTP connection is still held by the response object
// to allow the response content to be streamed directly from the network
socket.
// In order to ensure correct deallocation of system resources
// the user MUST either fully consume the response content or abort request
// execution by calling CloseableHttpResponse#close().
{quote}
but the [user
guide|http://hc.apache.org/httpcomponents-client-4.3.x/tutorial/html/fundamentals.html#d5e145]
says:
{quote}
The difference between closing the content stream and closing the response is
that the former will attempt to keep the underlying connection alive by
consuming the entity content while the latter immediately shuts down and
discards the connection.
{quote}
This is a contradiction. The code which follows in the quick start is correct
but not the comment. Even if I consume the response content the underlying
connection is still help open.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
-
To unsubscribe, e-mail: dev-unsubscr...@hc.apache.org
For additional commands, e-mail: dev-h...@hc.apache.org
