Server responding before all the data is read

["이희승 (Trustin Lee)"]

In Netty, an HTTP request can be split into multiple messages
(HttpRequest and HttpChunks).  Therefore, even if you received
HttpRequest, the whole request might not have been received yet.  You'd
better wait until the last HttpChunk is received before sending the 401
response in this case.  Please refer to HTTP snoop example to see how to
handle the HTTP messages in Netty.

HTH

On 01/01/2011 10:05 AM, Tom Byrne wrote:
> Here's my situation:
> 
> I have a fairly simple server that does some basic DAV like things,
> including an http PUT method. At the beginning of my processing, I do a
> basic authentication. In the cases where it fails, it appears that Netty
> is returning my 401 before the rest of the body has been read off the
> wire, causing some client confusion. 
> 
> I'm trying to get a simple use case, but offhand, can anyone throw out
> some ideas of what I might be doing wrong?
> 
> Thanks,
> Tom
> 
> 
> _______________________________________________
> netty-users mailing list
> netty-users at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/netty-users


-- 
Trustin Lee, http://gleamynode.net/

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 294 bytes
Desc: OpenPGP digital signature
Url : http://lists.jboss.org/pipermail/netty-users/attachments/20110502/47bdd2c0/attachment.bin