DO NOT REPLY [Bug 10541] - Content-length header should be automatically set for buffered Servlets/JSPs

2002-10-18 Thread bugzilla 
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=10541

Content-length header should be automatically set for buffered Servlets/JSPs

[EMAIL PROTECTED] changed:

   What|Removed |Added

 Status|RESOLVED|REOPENED
 Resolution|WONTFIX |



--- Additional Comments From [EMAIL PROTECTED]  2002-10-17 22:12 ---
I'll reopen the bug, since I also seem to have an itch with it. 
The major problem is that it's hard to know ( from connector side ) when
you have this case, and the END will follow imediately after the first
chunk. 
The only way to detect it is higher - and distinguish between a SEND that
happens normally and the SEND+END that happens when the JSP/servlet
finishes the request and the container is automatically flushing the buffer.

I don't see any other solution, at least at container level - you can't guess
that END will follow.

The problem is finding the exact point where the flushing happens.

Remy - if you want to close this, please mark it as REMIND or LATER, I'll
fix it ( if I figure out how :-)

--
To unsubscribe, e-mail:   
For additional commands, e-mail:

DO NOT REPLY [Bug 10541] - Content-length header should be automatically set for buffered Servlets/JSPs

2002-10-18 Thread bugzilla 
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=10541

Content-length header should be automatically set for buffered Servlets/JSPs

[EMAIL PROTECTED] changed:

   What|Removed |Added

 AssignedTo|tomcat- |[EMAIL PROTECTED]
   |[EMAIL PROTECTED]  |
 Status|REOPENED|NEW

--
To unsubscribe, e-mail:   
For additional commands, e-mail:

DO NOT REPLY [Bug 10541] - Content-length header should be automatically set for buffered Servlets/JSPs

2002-07-08 Thread bugzilla 

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=10541

Content-length header should be automatically set for buffered Servlets/JSPs

[EMAIL PROTECTED] changed:

   What|Removed |Added

 Status|REOPENED|RESOLVED
 Resolution||WONTFIX



--- Additional Comments From [EMAIL PROTECTED]  2002-07-08 18:48 ---
As I said, this won't be fixed in the old HTTP connector.

--
To unsubscribe, e-mail:   
For additional commands, e-mail:

DO NOT REPLY [Bug 10541] - Content-length header should be automatically set for buffered Servlets/JSPs

2002-07-08 Thread bugzilla 

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=10541

Content-length header should be automatically set for buffered Servlets/JSPs

[EMAIL PROTECTED] changed:

   What|Removed |Added

 Status|RESOLVED|REOPENED
 Resolution|WONTFIX |



--- Additional Comments From [EMAIL PROTECTED]  2002-07-08 18:40 ---
Please read the following comments - if you choose to set the bug
back to "resolved wontfix" I won't continue to reopen, but please
do consider the following first: (thanks)

1) The spec is not specifying how the transport layer behaves.
The spec is saying that asking a buffer to be used (even if used
by default as with JSP's) also includes
asking the container to set the content length for the servlet/jsp.
In other words, you can think if it in a similar manner to the actual
servlet saying "please call setContentLength()" for me.

2) HTTP 1.1 clearly does strongly encourage the use of the
Content-length header (or chunked transfer encoding instead)
whenever possible -- see sections 4.4, 10.4.12, and 14.14 in RFC 2616.

3) I don't see why you would need to change connectors to support this.
Normally, if a servlet programatically sets the content length,
the AJP connector passes this header along fine.
If the servlet sets a buffer size, this is in fact asking the servlet
container to set the content length for it -- at this point nothing
has yet been passed to the connector, so there is no reason for the
connector to know the difference between the two situations.
(let me know if I'm not explaining this clearly).

4) Recent versions of Commercial servlet containers (e.g. BEA Weblogic)
DO take care
of the content length in the buffered situation, as the spec says.
While this doesn't prove that what the spec says is the right thing to do,
I think it makes a great deal of sense.
I do hope you might re-consider adding this feature to Tomcat.

At any rate, thanks for all the great work you guys do!

--
To unsubscribe, e-mail:   
For additional commands, e-mail:

Re: DO NOT REPLY [Bug 10541] - Content-length header should be automatically set for buffered Servlets/JSPs

2002-07-08 Thread Simon Stewart 

On Mon, Jul 08, 2002 at 01:49:17AM -0700, vicky kak wrote:
> Hi,
>   I have already mailed you and informed you to remove
> myself from your mailing list,but it seems no action
> have been taken.I have mialed you on saturday but I
> still got the posts on monday.Please remove my id from
> your mailing list as I dont get the required mails.Hope
> to unsubscribed now..

Vicky, why not just follow the links at the bottom of all the emails
from this list? I include the line from your own post...

> To unsubscribe, e-mail:   

HTH. HAND.

Cheers,

Simon

-- 
"Even had to open up the case and gaze upon the hallowed peace that
graced the helpdesk that day." -- Megahal (trained on asr), 1998-11-06

--
To unsubscribe, e-mail:   
For additional commands, e-mail:

Re: DO NOT REPLY [Bug 10541] - Content-length header should be automatically set for buffered Servlets/JSPs

2002-07-08 Thread vicky kak 

Hi,
  I have already mailed you and informed you to remove
myself from your mailing list,but it seems no action
have been taken.I have mialed you on saturday but I
still got the posts on monday.Please remove my id from
your mailing list as I dont get the required mails.Hope
to unsubscribed now..
regards vicky

_
FindLaw - Free Case Law, Jobs, Library, Community
http://www.FindLaw.com
Get your FREE @JUSTICE.COM email!
http://mail.Justice.com

--
To unsubscribe, e-mail:   
For additional commands, e-mail:

DO NOT REPLY [Bug 10541] - Content-length header should be automatically set for buffered Servlets/JSPs

2002-07-08 Thread bugzilla 

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=10541

Content-length header should be automatically set for buffered Servlets/JSPs

[EMAIL PROTECTED] changed:

   What|Removed |Added

 Status|NEW |RESOLVED
 Resolution||WONTFIX



--- Additional Comments From [EMAIL PROTECTED]  2002-07-08 08:36 ---
Since both work fine and work transparently for a non broken HTTP/1.1 client,
the spec has no buisness specifying how the transport layer should behave. Also,
a number of intermediate protocols, like AJP, may not be able/willing to
implement the spec requirements.

I think the spec is broken here.

Coyote HTTP/1.1 does implement this requirement in some specific cases (many are
not implementable); the old HTTP connector will not be modified to fix it.

--
To unsubscribe, e-mail:   
For additional commands, e-mail: