Product: TIBCO Spotfire®
ERROR "The remote server returned error: (400) Bad Request" when logging into Spotfire Analyst
TIBCO Spotfire Analyst login error “The remote server returned error: (400) Bad Request”.
This issue may be seen in case of a Spotfire Server configured for KERBEROS authentication.
----------------------------------------------------------------------------
The remote server returns the error: (400) Bad Request. (HRESULT: 80131509)
Error message: Cannot connect to the specified server. Before trying again, make sure that the server you connect to is a valid Spotfire Server, that the server is running, and that you are connected to the network.
WebException at Spotfire.Dxp.Framework:
The remote server returned an error: (400) Bad Request . (HRESULT: 80131509)
Stack Trace:
at Spotfire.Dxp.Framework.HttpClient.NativeWebResponse..ctor(NativeHttpClient httpClient, NativeWebRequest request)
at Spotfire.Dxp.Framework.HttpClient.WinINet.WinINetWebRequest.GetResponseCore()
at Spotfire.Dxp.Framework.HttpClient.NativeWebRequest.GetResponse()
at Spotfire.Dxp.Framework.Login.WindowsIntegratedAuthenticator.Authenticate(SpotfireIdentity identity)
at Spotfire.Dxp.Loader.LoginHandler.PerformLogin()
-------------------------------------------------------------------------------------------------
The "(400) Bad Request" error is most often seen due to the HTTP request header exceeding the default max limit (16384). This can happen when the client is a member of many groups in the domain, causing the group's information to be included in the request and causing a long request header.
1). Locate the server.xml file, [server install dir]\tomcat\conf\server.xml .
2). Locate maxHttpHeaderSize size setting for Spotfire app:
< Service name="Spotfire">
<Connector port="80"
maxHttpHeaderSize="16384"
…
3). Change this setting to 65536:
maxHttpHeaderSize="65536"
4). Save the file.
NOTE:
On the Spotfire server, changing the maxHttpHeaderSize setting has proven effective.
Comments
0 comments
Article is closed for comments.