http error 400 request hostname is invalid

HTTP400 error is sometimes reported when Ajax requests background data-Invalid request (badrequest); Invalid error message stating that the request did not enter the background service;

HTTP 400 error is sometimes reported when Ajax requests background data-the request is invalid (bad requests), the request

When you visit a Web site today, an "HTTP Error 400" appears. The request is badly formed. " ErrorSo how do we fix it?1, Problem Description:"" HTTP error

Today's new site found in the Chrome browser, through localhost access is valid, but through the native IP even 127.0.0.1 access is not valid,The error in the report is that the Request Invalid HostNameSo that the site through two

this analysis, it is possible that IIS does not support put and delete predicate requests.The new add verb put and delete are added to IIS through Baidu again. Click on deploy Apps--Come Out program map –> Aspnetcore (because I'm deploying a. Net Core program, so select the Aspnetcoremodule module)Double-click OpenBy checking that the Aspnetcore itself is supporting all predicates, it

Site access error Bad Request (Invalid Hostname), as shown below: Analysis: "Bad Request (Invalid Hostname)" is the literal translation

Generally, when we see a Bad Request (Invalid Hostname) error on the website, we will say that it is iis. If there is a problem with apache, the solution to this problem in iis is proba

persists, contact the administrator of your WEB server.HTTP Error 500500 internal error of the serverThe WEB server cannot perform this request. Please retry this request later.If the problem persists, contact the administrator of your Web server.HTTP Error 501501 Not imple

Error logging in the server is similar to this: 124.65.133.242––[27/oct/2014:14:30:51 +0800] "-" 400 0 "-" "-"124.65.133.242––[27/oct/2014:14:31:45 +0800] "-" 400 0 "-" "-"124.65.133.242––[27/oct/2014:14:31:45 +0800] "-" 400 0 "-" "-"124.65.133.242––[27/oct/2014:14:31:45 +0

#400/500 error retry # When the service returns the 400/500 status and has a surviving node in the current pool, reset the HTTP request and reselect the node in the pool. # Accept the new HTTP

Code:@InitBinder public void Initbinder (Webdatabinder binder) { SimpleDateFormat DateFormat = new SimpleDateFormat ( "Yyyy-mm-dd"); Dateformat.setlenient (false); Binder.registercustomeditor (Date.class, New Customdateeditor (DateFormat, false)); }SimpleDateFormat ("YYYY-MM-DD") the format passed in must be the format that the foreground passes over,Then run, or error, the last discovery is