Re: protocol/2032: When a POST or GET contains more than exactly 480 chars (CONTENT_LENGTH) improper headers SEEM to be sent

1998-09-13 Thread fielding
[In order for any reply to be added to the PR database, ] [you need to include <[EMAIL PROTECTED]> in the Cc line ] [and leave the subject line UNCHANGED. This is not done] [automatically because of the potential for mail loops. ] [If you do not include this Cc, your reply may be ig- ] [nored un

Re: protocol/2032: When a POST or GET contains more than exactly 480 chars (CONTENT_LENGTH) improper headers SEEM to be sent

1998-04-07 Thread dgaudet
[In order for any reply to be added to the PR database, ] [you need to include <[EMAIL PROTECTED]> in the Cc line ] [and leave the subject line UNCHANGED. This is not done] [automatically because of the potential for mail loops. ] Synopsis: When a POST or GET contains more than exactly 480 chars

Re: protocol/2032: When a POST or GET contains more than exactly 480 chars (CONTENT_LENGTH) improper headers SEEM to be sent

1998-04-06 Thread Dean Gaudet
The following reply was made to PR protocol/2032; it has been noted by GNATS. From: Dean Gaudet <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Subject: Re: protocol/2032: When a POST or GET contains more than exactly 480 chars (CONTENT_LENGTH) improper headers SEEM to b

protocol/2032: When a POST or GET contains more than exactly 480 chars (CONTENT_LENGTH) improper headers SEEM to be sent

1998-04-03 Thread Resnick
>Number: 2032 >Category: protocol >Synopsis: When a POST or GET contains more than exactly 480 chars >(CONTENT_LENGTH) improper headers SEEM to be sent >Confidential: no >Severity: serious >Priority: medium >Responsible:apache >State: open >Class: