chris
derham
Gesendet: Mittwoch, 5. Oktober 2011 12:53
An: Tomcat Users List
Betreff: Re: AW: ISAPI Redicect - Request Entitiy too large
Alexander,
If you are using authorisation header, then you are using SPNGEO. This
header encodes the users group membership in the authorisation header. By
default
Alexander,
If you are using authorisation header, then you are using SPNGEO. This
header encodes the users group membership in the authorisation header. By
default tomcat has an 8k maximum header, whilst users belonging to many
groups can have an authorisation token that can swell to larger than t
n.c (469): failed appending the header
value
[Fri Sep 30 15:06:08.460 2011] [3456:1540] [info]
ajp_service::jk_ajp_common.c (2431): Creating AJP message failed, without
recovery
[Fri Sep 30 15:06:08.460 2011] [3456:1540] [error]
HttpExtensionProc::jk_isapi_plugin.c (2261): service() failed with
Addendum : can you increase the log level of isapi_redirect on the IIS server, and try
again ? it may show us a bit more about what is happening.
André Warnier wrote:
Alexander Diedler wrote:
Hello,
We use the IIS integrated (Windows) domain authentication, which is
passed
to the Tomcat and
Alexander Diedler wrote:
Hello,
We use the IIS integrated (Windows) domain authentication, which is passed
to the Tomcat and then we check the given String with our user database in
the app and if username and password match, the user was "automatically"
logged in (SSO).
Ok, basically thanks.
Hello,
We use the IIS integrated (Windows) domain authentication, which is passed
to the Tomcat and then we check the given String with our user database in
the app and if username and password match, the user was "automatically"
logged in (SSO).
Greetings
Alexander
-Ursprüngliche Nachricht-
