guess it is written in c language. :-)
Please let me know if I should do further tests (though there is nothing
more I can think of).
Thank you,
Br1.
--
View this message in context:
http://www.nabble.com/JK-connector-fails-with-long-URLs-tp21443475p21545131.html
Sent from the Tomcat
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,
-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
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
-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
to put
his hands on the code. And avoid the need to correct and recompile every
time a new version comes out..
Thank you for the hints,
Br1.
--
View this message in context:
http://www.nabble.com/JK-connector-fails-with-long-URLs-tp21443475p21511740.html
Sent from the Tomcat - User mailing list
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-tp21443475p21478016.html
Sent from the Tomcat - User mailing list archive at Nabble.com
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
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 list archive at Nabble.com
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
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-tp21443475p21443475.html
Sent from the Tomcat - User mailing list archive at Nabble.com
11 matches
Mail list logo