tomcat-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Henri Gomez" <>
Subject Re: configurable AJP Buffer Size
Date Thu, 06 Apr 2006 11:34:04 GMT
Just take a look at the AJP protocol documentation :

Packets sent from the server to the container begin with 0x1234.
Packets sent from the container to the server begin with AB (that's
the ASCII code for A followed by the ASCII code for B). After those
first two bytes, there is an integer (encoded as above) with the
length of the payload. Although this might suggest that the maximum
payload could be as large as 2^16, in fact, the code sets the maximum
to be 8K.

So to support more than 64k bytes, we should have a whole new code on
Apache and Tomcat side and break compatibility with all current
implementations. And that's bad ;(

Take a look at the AJP13 extension proposal :

We could plug many usefull informations in LOGIN INIT for example !

2006/4/6, KARNATI, SRINIVASA R [AG/1000] <>:
> >>-----Original Message-----
> >>From: Mladen Turk []
> >>Sent: Thursday, April 06, 2006 12:57 AM
> >>To: Tomcat Developers List
> >>Subject: Re: configurable AJP Buffer Size
> >>
> >>Henri Gomez wrote:
> >>> well client and server should be in phase about the buffer size and
> >>> the better way to accomplish that will be via AJP13 extensions (ie
> >>> AJP14), with connect time negociation datas like packet buffer size :)
> >>>
> >>
> >>Right. Extensions could contain packet size. The problem is that even
> >>with the custom size that size would be limited to 32K, and again
> >>someone will complain about that limitation ;)
> Possible. But, I have no idea why connector should be constraining this.
> ---------------------------------------------------------------------------------------------------------
> This e-mail message may contain privileged and/or confidential information, and is intended
to be received only by persons entitled to receive such information. If you have received
this e-mail in error, please notify the sender immediately. Please delete it and all attachments
from any servers, hard drives or any other media. Other use of this e-mail by you is strictly
> All e-mails and attachments sent and received are subject to monitoring, reading and
archival by Monsanto. The recipient of this e-mail is solely responsible for checking for
the presence of "Viruses" or other "Malware". Monsanto accepts no liability for any damage
caused by any such code transmitted by or accompanying this e-mail or any attachment.
> ---------------------------------------------------------------------------------------------------------
> ---------------------------------------------------------------------
> To unsubscribe, e-mail:
> For additional commands, e-mail:

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

View raw message