Hi, Thank you.. if this was this easy.. :-) Unfortunately, one of their requirements is to send the URLs by email.
I already told them to use a different method, but I still hope to see an higher limit in the next JK version. Thanks again, Br1. awarnier wrote: > > br1 wrote: >> >> Rainer Jung-3 wrote: >>> It looks like we only support URLs up to 2047 Bytes (+/- 1). >>> >>> Regards, >>> >>> Rainer >>> >> >> Hey Rainer, >> >> Do you think this limit will be increased in the next versions? >> >> In theory, no limit is imposed by the protocol itself. I would tend to >> think >> JK should at least support what the JK supported platforms support. >> >> What is annoying - at least on IIS - is that all requests get blocked, >> not >> just the ones getting redirected to Tomcat. This limit is not present on >> any >> other ISAPI filter I know. >> >> Don't get me wrong: my personal opinion is that 2k are more than enough >> for >> any URL, but the only place I can impose this limit is at home. And maybe >> not for much longer. :-) >> > > <form enctype="multipart/form-data"> > has the browser send request parameters in the body of the request, > instead of the URL. No 2K limit there. > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org > For additional commands, e-mail: users-h...@tomcat.apache.org > > > -- View this message in context: http://www.nabble.com/JK-connector-fails-with-long-URLs-tp21443475p21496454.html Sent from the Tomcat - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
