Oleg Kalnichevski wrote:
On Tue, 2011-01-04 at 19:32 +0100, Oleg Kalnichevski wrote:
In which case HttpClent would use chunk coding to signal the end of the message
body. That means there would be at least a closing tag.
I don't know HttpClient like you, but once I put some content in the
fi
On Tue, 2011-01-04 at 19:32 +0100, Oleg Kalnichevski wrote:
> > >>>
> > > In which case HttpClent would use chunk coding to signal the end of the
> > > message body. That means there would be at least a closing tag.
> >
> > I don't know HttpClient like you, but once I put some content in the
> >
> >>>
> > In which case HttpClent would use chunk coding to signal the end of the
> > message body. That means there would be at least a closing tag.
>
> I don't know HttpClient like you, but once I put some content in the
> file everything works.
> >
Please produce wire log of the HTTP sessio
Oleg Kalnichevski wrote:
"Ittay Dror" wrote:
Oleg Kalnichevski wrote:
"Ittay Dror" wrote:
Oleg Kalnichevski wrote:
On Tue, 2011-01-04 at 17:30 +0200, Ittay Dror wrote:
It turns out this is because my warmupInput file was empty. The
server
responded with 100 (continue), but because
"Ittay Dror" wrote:
>
>
>Oleg Kalnichevski wrote:
>> "Ittay Dror" wrote:
>>
>>>
>>> Oleg Kalnichevski wrote:
On Tue, 2011-01-04 at 17:30 +0200, Ittay Dror wrote:
> It turns out this is because my warmupInput file was empty. The
>>> server
> responded with 100 (continue), but because
Oleg Kalnichevski wrote:
"Ittay Dror" wrote:
Oleg Kalnichevski wrote:
On Tue, 2011-01-04 at 17:30 +0200, Ittay Dror wrote:
It turns out this is because my warmupInput file was empty. The
server
responded with 100 (continue), but because the file was empty
nothing
was written to the ou
"Ittay Dror" wrote:
>
>
>Oleg Kalnichevski wrote:
>> On Tue, 2011-01-04 at 17:30 +0200, Ittay Dror wrote:
>>> It turns out this is because my warmupInput file was empty. The
>server
>>> responded with 100 (continue), but because the file was empty
>nothing
>>> was written to the output stream, so
Oleg Kalnichevski wrote:
On Tue, 2011-01-04 at 17:30 +0200, Ittay Dror wrote:
It turns out this is because my warmupInput file was empty. The server
responded with 100 (continue), but because the file was empty nothing
was written to the output stream, so after a while there was a timeout.
IM
On Tue, 2011-01-04 at 17:30 +0200, Ittay Dror wrote:
> It turns out this is because my warmupInput file was empty. The server
> responded with 100 (continue), but because the file was empty nothing
> was written to the output stream, so after a while there was a timeout.
>
> IMHO, this is a bug.
It turns out this is because my warmupInput file was empty. The server
responded with 100 (continue), but because the file was empty nothing
was written to the output stream, so after a while there was a timeout.
IMHO, this is a bug. Either an empty input should be posted, or I should
get a mo
Hello
I'm trying to send a POST request to "http://localhost:8090/my/path";,
and getting the exception in the subject.
The request goes to a the same process.
The servlet handling requests is jersey's ServletContainer.
Requests from an external tool (both to http://localhost:8090/my/path
and
11 matches
Mail list logo
