search

inevity / lusca-cache

Automatically exported from code.google.com/p/lusca-cache
0 stars 0 forks source link

excess reply data for a reply which should have no reply body #35

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago 
Lusca correctly logs and closes replies with excess reply body data. It
doesn't pass the reply body up to the client. But it confusingly logs the
same error whether there was too much reply body data OR whether the reply
body wasn't expected in the first place.

Please document and clarify this!

Original issue reported on code.google.com by adrian.c...@gmail.com on 1 Jul 2009 at 7:47

GoogleCodeExporter commented 9 years ago 
The request/reply info is here:
http://code.google.com/p/lusca-cache/wiki/HttpWeirdnessReplyBodyWhereNotExpected

Original comment by adrian.c...@gmail.com on 1 Jul 2009 at 7:52

GoogleCodeExporter commented 9 years ago 
r14107 attempts to clarify this. I absolutely don't like the current structure 
of the
reply code and where this check is handled. I'm not even sure I'm correctly 
capturing
the situation(s) here. In any case, it should help narrow down the suspect URLs 
to
investigate "excess data" from to see if there are truely any cases that merit 
checking.

Original comment by adrian.c...@gmail.com on 1 Jul 2009 at 8:01