Re: JK connector fails with long URLs

2009-01-19 Thread Christopher Schultz
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Br1, br1 wrote: > Ok, I am starting to understand better what is happening, there seem to be > two problems here. > > 1 - The max URL length for IIS 5 is about 2k or so. This cannot be changed > probably. That's what my knee-jerk reaction was to s

Re: JK connector fails with long URLs

2009-01-19 Thread Mladen Turk
br1 wrote: My suggestion to the developers here, could you please intercept the error and maybe return a "413 Request Entity Too Large" message? This is what happens for instance with Ionics rewrite (see 31 october 2008 release, http://www.codeplex.com/IIRF/SourceControl/ListDownloadableCommits

Re: JK connector fails with long URLs

2009-01-19 Thread br1
hose URL+query string exceeds the max URL length value, not just the ones being AJP redirected to Tomcat. 3 - Chris, taking a look at the code shed some light, but don't ask me to change the code, I can hardly guess it is written in c language. :-) Please let me know if I should do f

Re: JK connector fails with long URLs

2009-01-16 Thread br1
y not that good at this, and I would prefer not to take this responsibility.. I am quite protective with my prod servers. :-) Should this be a bug, I would prefer to wait someone that knows where to put his hands on the code. And avoid the need to correct and recompile every time a new version come

Re: JK connector fails with long URLs

2009-01-16 Thread Christopher Schultz
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Br1, br1 wrote: > 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. The source code

Re: JK connector fails with long URLs

2009-01-16 Thread br1
se this limit is at home. And maybe >> not for much longer. :-) >> > > > has the browser send request parameters in the body of the request, > instead of the URL. No 2K limit there. > > > --------- > To

Re: JK connector fails with long URLs

2009-01-15 Thread André Warnier
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

Re: JK connector fails with long URLs

2009-01-15 Thread br1
at 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. :-) Thank you, Br1. -- View this message in context: http://www.nabble.com/JK-connector-fails-with-long-URLs-tp21443475p21489226.html Sent from the Tomcat - User mailing

Re: JK connector fails with long URLs

2009-01-15 Thread Rainer Jung
On 15.01.2009 14:53, br1 wrote: Additional info: - Machines are IIS 5 on Windows 2000 Server - Though the same happens on my XP laptop - The JK log shows this error message, with the line number varying between JK versions, here is the 1.2.27 one: [error] jk_isapi_plugin.c (1852): error while get

Re: JK connector fails with long URLs

2009-01-15 Thread br1
n for > non existing files > - the problem does not appear when I remove the JK ISAPI filter. > > What should I do? > > Thank you in advance, > Br1 > > > -- View this message in context: http://www.nabble.com/JK-connector-fails-with-long-URLs-tp2144

JK connector fails with long URLs

2009-01-13 Thread br1
appear when I remove the JK ISAPI filter. What should I do? Thank you in advance, Br1 -- View this message in context: http://www.nabble.com/JK-connector-fails-with-long-URLs-tp21443475p21443475.html Sent from the Tomcat - User mailing list archive at Nabble.com