http error 400 request verb is invalid

nginx:400 Bad Request | The plain HTTP request is sent to HTTPS portNginx version nginx/1.12.2Problem 400 error using SSL link in Nginx environmentThe Nginx configuration file

, add the following configuration under the,[XML]View Source code copy Print security> requestfiltering> requestlimits maxquerystring="4080" /> requestfiltering> Security> For already set, you can modify the size of the maxquerystring2, for all projects to apply this configuration, in the C:\Windows\System32\inetsrv\config found applicationhost.config files, in the,[XML]View Source code copy Print security> requestfiltering> requestlimi

In recent days, when the interface was developed, Tomcat reported 400 errors and looked for the following reasons.Error cause : The parameters section of the URL contains/, the default tomcat is not supported URL parameters include:/(%2F), \ (%5c).parsing method : can be configured by adding dorg.apache.tomcat.util.buf.udecoder.allow_encoded_slash=trueMethod 1: Modify the configuration file, tomcat6/conf/

After upgrading to IOS9, the default request type is HTTPS, and how to use HTTP to request an errorThe resource could not being loaded because the APP Transport Security policy requires the use of a secure connection.Cause IOS9 introduces a new featureApp Transport Security (ATS)The new feature requires that the networ

Note: This article is from the blog "afei". If you want to repost this article, please contact the author! And indicate the source: http://blog.csdn.net/faye0412/article/details/7970155 These two days, I suddenly received the test team and told the company that the android client should be used on some mobile phones with the following exceptions, some of which were running well and were very strange: 1)

phenomenon : The site set for the AD integration certification, but when the visit is prompted to enter account password. Three times after the error occurred. Scenario : Run under C:\Inetpub\Adminscripts: cscript adsutil.vbs set w3svc/ntauthenticationproviders "NTLM" modifies the validation mechanism. The original text reads as follows: http://support.microsoft

The reason is that jersey built-in converters can only do simple type conversions such as:The client must first submit a string;String----> String/long/boolean These basic can be converted, but if you write as follows:String---->date type, then jersey internal error, reported the illegal request message, can not be debugged (took 2 days to understand, do not repe

Possible cause: Multipartresolver Not configured correctlySee the solution:file Upload ID must be multipartresolver, or error http Status 400–bad Request - BeanID= "Multipartresolver"class= "Org.springframework.web.multipart.commons.CommonsMultipartResolver"> Propertyname= "Defaultencoding"value= "UTF-8"/>

power of the server.414 (The requested URI is too long) The requested URI (usually the URL) is too long for the server to process.415 (Unsupported media type) The requested format is not supported by the requested page.416 (The request scope does not meet the requirements) if the page cannot provide the requested scop

Introduction to the problem Whenever an HTTP error code is encountered that is 400, a request initiated on behalf of the client does not conform to some of the server's restrictions on the re