Bill: If I make modifications to isapi_redirect.dll and the Java side of the Connector, what is the possibility of getting them included in the future releases of the production code? I asked this because we also should be able to use future releases, or at least until AJP/1.4 alleviates this issue.
- Srini -----Original Message----- From: news [mailto:[EMAIL PROTECTED] On Behalf Of Bill Barker Sent: Monday, December 05, 2005 9:02 PM To: users@tomcat.apache.org Subject: Re: AJP13: request headers > max packet size I'm afraid that the 8KB limit is part of the AJP/1.3 protocol, so it is very unlikely to get "fixed" until AJP/1.4. At the moment, AJP/1.4 is just vapor-ware ;-). To do anything else would likely break too many installations in very horrible ways. Of course, you're free to modify the source for isapi_redirect.dll to change the size (you'll have to make the corresponding change to the Java side of the Connector). "KARNATI, SRINIVASA R [AG/1000]" <[EMAIL PROTECTED]> wrote in message news:[EMAIL PROTECTED] .. We have run into 8 kb (max packet size) limit. We are using Kerberos authentication in Active Directory environment. For some of our application users Kerberos ticket that gets passed via HTTP header exceeds 8 kb. The debug log shows connector fails even before trying to send headers. We are using IIS with isapi_redirector2.dll. In another scenario we have IIS with isap_redirect.dll (2.1.15.) Unfortunately, using HTTP (8080) connector is not an option. I am wondering if MAX_PACKET_SIZE can be passed as configurable option, or if this could be fixed in future releases of the connector? Thanks, Srini ---------------------------------------------------------------------------- ----------------------------- 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 prohibited. 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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
