[
https://issues.apache.org/jira/browse/HTTPCLIENT-1008?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Oleg Kalnichevski resolved HTTPCLIENT-1008.
---
Resolution: Fixed
Fix Version/s: (was: 4.1.0)
[
https://issues.apache.org/jira/browse/HTTPCLIENT-1008?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michajlo Matijkiw updated HTTPCLIENT-1008:
--
Attachment: negotiated_response_updated.patch
That was indeed the case, up
[
https://issues.apache.org/jira/browse/HTTPCLIENT-1008?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12921415#action_12921415
]
Jonathan Moore commented on HTTPCLIENT-1008:
This was probably caused beca
[
https://issues.apache.org/jira/browse/HTTPCLIENT-1008?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12921411#action_12921411
]
Oleg Kalnichevski commented on HTTPCLIENT-1008:
---
Michajlo,
One of the t
[
https://issues.apache.org/jira/browse/HTTPCLIENT-1011?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Oleg Kalnichevski resolved HTTPCLIENT-1011.
---
Resolution: Fixed
Fix Version/s: 4.1 Alpha3
Patch checked in. Man
[
https://issues.apache.org/jira/browse/HTTPCLIENT-1009?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12921383#action_12921383
]
Oleg Kalnichevski commented on HTTPCLIENT-1009:
---
Patch checked in. Many
On Fri, 2010-10-15 at 16:56 +0530, Supun Kamburugamuva wrote:
> On Fri, Oct 15, 2010 at 10:38 AM, Asankha C. Perera wrote:
>
> >
> > In my case there is no stack trace. The browser is the client. Browser
> >> waits
> >> for the data to come but I can clearly see that the page has transferred
> >>
On Fri, 2010-10-15 at 00:52 +0100, sebb wrote:
> The site currently uses -ga and -dev soft links to make it easier to
> update the html links.
>
> However, examples are currently referenced from SVN tags, which makes
> it a bit tedious to update them.
>
> Just wondering if there is a better way t
On Fri, Oct 15, 2010 at 10:38 AM, Asankha C. Perera wrote:
>
> In my case there is no stack trace. The browser is the client. Browser
>> waits
>> for the data to come but I can clearly see that the page has transferred
>> to
>> the browser. This means that the chunking is incorrect and browser th