sip 400 bad request

Yesterday we handled the 500 error in Google Webmaster and handled some 400 processing today, such as the following URL at the End of tab (tab):http://www.cnblogs.com/me-sa/archive/2008/05/16/1200329.html%09http://www.cnblogs.com/JimmyZhang/archive/ 2007/12/20/1006555.html%09 ...When these URLs are accessed, IIS returns the error of the "Bad Request":

Recently Angularjs post to background 4,001 header fog without any errors.Finally found a good article, thank the authorThe solution to the "bad Request" error in SPRINGMVC (using @responsebody to process the JSON data transmitted by Ajax into the Bean)In today's development process, there was an error in the action in SPRINGMVC that processed the JSON data from the foreground AJAX

Development tools: VS2010, Development components: WebService, operating Environment: WindowsToday, a colleague in the billing interface debugging, found a very strange problem: the interface in the home environment testing, everything is normal, but after deployment to the current network environment, successive calls to the interface will be error: The remote server returned an errors: (400) Bad

Today, when the project was suddenly reported a bad request error, the backstage did not have any problems.First I looked at the log log does not receive any parameters, you can determine that the request is not sent out, so it should be the foreground data submission problem.Then I saw some tips from some netizens:1. The Submission form data type does not match

In today's development process, there was an error in the action in SPRINGMVC that processed the JSON data from the foreground AJAX request directly into the corresponding entity class: The bad request, the background is not an error, 400 refers to invalid requests (the request