on ‎2008 Jun 05 1:31 PM
Hi Guys,
Need help here. This error occurs at random in the KM and also by randam content editors. They navigate into the "Explorer" of Content Management and follow the folder structure created for their content. Upon triggering to open a folder in teh structure, the content editors sometimes get the error message: "400 Bad HTTP request". This happens to afew of them so often, such that every clicks within the folder structures all ended in the same error.
At first I thought it could be a hardware issue, so I log on to the same hardware with my userID and I do not have any problems (no 400 error message). I even ask the user to try it on a different hardware and he does not get any error with a new hardware. However, after afew weeks, the 400 error occur again for the same users with new hardware.
Does anyone experience the same issue as me?
Thanks.
Ray
Request clarification before answering.
Hi,
This occurs when the HTTP Request that is generated from browser is not understood by server.
So enable your Web browser to support http 1.1 by going to menu Tools--> Internet Options --> Advanced.
If http 1.1 is already enable, then uncheck it, anb see if this fixes the problem.
Regards,
Praveen Gudapati
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi
i never this error so far but this this is the exact reason for this error in http world
400 errors in the HTTP cycle
Any client (e.g. your Web browser or our CheckUpDown robot) goes through the following cycle:
Obtain an IP address from the IP name of your site (your site URL without the leading 'http://'). This lookup (conversion of IP name to IP address) is provided by domain name servers (DNSs).
Open an IP socket connection to that IP address.
Write an HTTP data stream through that socket.
Receive an HTTP data stream back from your Web server in response. This data stream contains status codes whose values are determined by the HTTP protocol. Parse this data stream for status codes and other useful information.
This error occurs in the final step above when the client receives an HTTP status code it recognises as '400'.
Resolving 400 errors - general
There is a low-level program bug in the client or the Web server or both. If you do not have access to the source code for these systems, the only thing you can do is refer the problem to technical support people at the companies that developed the systems.
Regards,
vijay.
| User | Count |
|---|---|
| 9 | |
| 5 | |
| 4 | |
| 4 | |
| 4 | |
| 3 | |
| 3 | |
| 2 | |
| 2 | |
| 2 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.