Filip Hanik - Dev Lists wrote:
>
> you're wrong, I believe it is
>
> chunk-header:blabla
> chunk-data
>
> The spec says
>
>chunk = chunk-size [ chunk-extension ] CRLF
> chunk-data CRLF
>
>
> Hence, the request that was posted here, should have been 16b
you're wrong, I believe it is
chunk-header:blabla
chunk-data
The spec says
chunk = chunk-size [ chunk-extension ] CRLF
chunk-data CRLF
Hence, the request that was posted here, should have been 16bytes
header, not 18
Filip
On 04/01/2010 11:23 AM, M
Filip Hanik - Dev Lists wrote:
>
> I just skimmed this through, but from what I remember, the CRLF after
> should not be counted into your "chunk header"
No, the chunk-size is the entire length of the chunk. Since a chunked
content-body can include any sort of data, it wouldn't make sense to
exc
On 03/31/2010 09:29 AM, Christian Pfeiffer wrote:
31 32
Let's take a look at the data you are sending
0040 36 17 31 32 0d 0a 3c 78 6d 6c 3e 48 65 6c 6c 6f 6.12..Hello
0050 3c 2f 78 6d 6c 3e 0d 0a ..
Your Chunk header: 31 32
That represents : 12
Which means, Tomcat will expect 18 bytes aft
Here the raw data:
No. TimeSourceDestination Protocol
Info
1 0.00127.0.0.1 127.0.0.1 TCP
46356 > http-alt [SYN] Seq=0 Win=32792 Len=0 MSS=16396 TSV=5912087
TSER=0 WS=6
Frame 1 (74 bytes on wire, 74 bytes captured)
I would need the raw data, not copy paste, I can't make anything out of
that. Or if you have, a simple test case.
Filip
On 03/31/2010 07:57 AM, Christian Pfeiffer wrote:
Hey Filip, thanks for your swift response. Wireshark tells me:
//Client//
POST /url/servlet HTTP/1.1
Host: localhos
Hey Filip, thanks for your swift response. Wireshark tells me:
//Client//
POST /url/servlet HTTP/1.1
Host: localhost:8080
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.0.13)
Gecko/2009080315 Ubuntu/9.04 (jaunty) Firefox/3.0.13
Transfer-Encoding: chunked
145
//Serve
hi Chris, if the connection is closed, most likely there is some sort of
data error somewhere.
Record your transaction with Wireshark, and we can examine it.
Low latency http, meaning sending traffic back and forth should be
possible within the body of the request
Filip
On 03/31/2010 07:01 A
Hello,
I just tried to use the tomcat nio and wondered if it is possible to use
client and server pushes through the same socket connection? Or if I
have to establish to connections for that purpose. In the end the client
should be able to receive notification from server (server push) and
al
