On Fri, 2011-01-07 at 22:32 +, sebb AT ASF wrote:
> It looks like something similar could be done for the maven-jar-plugin
> - at present the manifest entries are defined in each of the component
> POMs.
>
> I think those 3 definitions could be merged into the httpclient parent.
>
> Thoughts?
It looks like something similar could be done for the maven-jar-plugin
- at present the manifest entries are defined in each of the component
POMs.
I think those 3 definitions could be merged into the httpclient parent.
Thoughts?
On 7 January 2011 22:28, wrote:
> Author: sebb
> Date: Fri Jan
On 7 January 2011 13:38, Oleg Kalnichevski wrote:
> Folks
>
> HttpClient 4.1 GA and HttpAsyncHttpClient 4.0-alpha1 releases are
> expected next week provided no release blockers are reported in the next
> few days.
>
> Please do try to find time to test the latest build of HttpClient for
> compati
[
https://issues.apache.org/jira/browse/HTTPCLIENT-1042?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12978866#action_12978866
]
Thorsten Scherler commented on HTTPCLIENT-1042:
---
Thank you very much Jon
On Fri, 2011-01-07 at 09:36 -0500, Jon Moore wrote:
> Hi Thorsten,
>
>
> I'm not able to reproduce your problem for part I (I haven't had a
> chance to look into the context-based status stuff yet, but will do so
> shortly). Perhaps I'm not issuing the same requests you are, though.
> Am I right
dev@hc.apache.org
-
To unsubscribe, e-mail: dev-unsubscr...@hc.apache.org
For additional commands, e-mail: dev-h...@hc.apache.org
[
https://issues.apache.org/jira/browse/HTTPCLIENT-1042?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jon Moore closed HTTPCLIENT-1042.
-
Resolution: Invalid
Assignee: Jon Moore
Not sure whether to mark this as invalid or ca
[
https://issues.apache.org/jira/browse/HTTPCLIENT-1042?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jon Moore updated HTTPCLIENT-1042:
--
Attachment: thorsten-test-cases.patch
This patch adds two passing test cases, depending on
[
https://issues.apache.org/jira/browse/HTTPCLIENT-1042?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12978807#action_12978807
]
Jon Moore commented on HTTPCLIENT-1042:
---
Hi Thorsten,
This patch breaks a numbe
[
https://issues.apache.org/jira/browse/HTTPCLIENT-1042?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Thorsten Scherler updated HTTPCLIENT-1042:
--
Attachment: 1042.patch
> CachingHttpClient should use conditionalRequest i
CachingHttpClient should use conditionalRequest instead of the request in the
suitabilityChecker calls
--
Key: HTTPCLIENT-1042
URL: https://issues.apache.org/jira/
Hi Thorsten,
I'm not able to reproduce your problem for part I (I haven't had a chance to
look into the context-based status stuff yet, but will do so shortly).
Perhaps I'm not issuing the same requests you are, though. Am I right that
in steps 2, 4, and 5 you are issuing conditional requests into
Folks
HttpClient 4.1 GA and HttpAsyncHttpClient 4.0-alpha1 releases are
expected next week provided no release blockers are reported in the next
few days.
Please do try to find time to test the latest build of HttpClient for
compatibility with your applications and report issues if found.
You ma
Hi all,
I am using the CachingHttpClient to test whether our site returns the
correct status for the following test.
1) request page -> returns 200
2) do it again -> returns 304
3) run a change on the source so last modified changes
4) request page -> returns 200
5) do it again -> returns 304
I
14 matches
Mail list logo