head	1.5;
access;
symbols;
locks
	nobody:1.5; strict;
comment	@# @;


1.5
date	99.06.09.17.06.24;	author nobody;	state Exp;
branches;
next	1.4;

1.4
date	99.06.09.05.23.02;	author nobody;	state Exp;
branches;
next	1.3;

1.3
date	99.06.09.05.22.41;	author nobody;	state Exp;
branches;
next	1.2;

1.2
date	99.06.09.05.22.35;	author nobody;	state Exp;
branches;
next	1.1;

1.1
date	99.06.09.05.22.31;	author nobody;	state Exp;
branches;
next	;


desc
@null
@


1.5
log
@null
@
text
@IDependOn-Set: 1
IDependOn-Set: 119
IDependOn-Set: 2
IDependOn-Set: 204
IDependOn-Set: 205
IDependOn-Set: 206
LastModifiedSecs: 928905781
Parent: 119
SequenceNumber: 2
Title: When I call HttpUtils.parsePostData() all the POST data is eaten by Apache Jserv. Is this a bug? 
Part: 0
Author-Set: jon@@working-dogs.com
HideAttributions: 1
LastModifiedSecs: 928905781
Type: 
Lines: 1
A servlet engine is only supposed to read (and thus eat) the POST data by calling parsePostData() when parsePostData() would actually be able to handle it, i.e. the content-type is "application/x-www-urlencoded". If the content-type is something else, like "multipart/form-data" (or "text/html" when a HTML document is PUT from Netscape Composer), the POST data should be left to the servlet itself to handle. (Thanks for Vincent Partington)
EndPart: 0
@


1.4
log
@null
@
text
@d6 1
d15 1
@


1.3
log
@null
@
text
@d6 1
a6 1
LastModifiedSecs: 928905761
d8 1
a8 1
SequenceNumber: 1
d10 7
@


1.2
log
@null
@
text
@d6 1
a6 1
LastModifiedSecs: 928905751
d8 2
a9 2
SequenceNumber: 0
Title: New Item
@


1.1
log
@null
@
text
@d4 1
@
