Springboot error
Ignore the empty nacos configuration and get it based on dataIdCurl test error
< HTTP/1.1 400
< Content-Type: text/html;charset=utf-8
< Content-Language: en
< Content-Length: 435
< Date: Fri, 03 Sep 2021 03:06:16 GMT
< Connection: close
<
* Closing connection 0
<!doctype html><html lang="en"><head><title>HTTP Status 400 – Bad Request</title><style type="text/css">body {font-family:Tahoma,Arial,sans-serif;} h1, h2, h3, b {color:white;background-color:#525D76;} h1 {font-size:22px;} h2 {font-size:16px;} h3 {font-size:14px;} p {font-size:12px;} a {color:black;} .line {height:1px;background-color:#525D76;border:none;}</style></head><body><h1>HTTP Status 400 – Bad Request</h1></body></html>Original request address
http://private_ appstore_ cloud_ nacos:8848
Modify container name and new request address
http://private-appstore-cloud-nacos:8848
Through curl test, it is found that the original request address server responds to 400 and the new address responds to 200. The reason is that the Nacos server determines that the HTTP protocol header host contains non-standard domain name characters.
Read More:
- When docker starts tomcat, the access port of the container displays 404, and the source server fails to find the representation of the target resource or is unwilling to disclose an existing one
- IIS “Bad Request – Request Too Long. HTTP Error 400. The size of the request headers is too long.”
- Error running docker container: starting container process caused “exec: \“python\“: executable file
- K8s deployment of single node Nacos error server is down now, please try again later
- NACOS error com.alibaba.nacos.api.exception.NacosException: failed to req API:/api//nacos/v1/ns/instance
- Docker start error: failed to start docker application container engine.
- Get connection timeout retry: 1 MySQL errorcode 0, state 08s01 docker container accessing MySQL container is very slow and sometimes interrupted
- Bad Request – Request Too Long. HTTP Error 400. The size of the request headers is too long
- The error record when docker starts Nacos, and the solution to the problem of port occupation
- NS_ERROR_DOM_BAD_URI: Access to restricted URI denied
- HTTP 400 error – bad request
- ajax error 400 (Failed to load resource: the server responded with a status of 400 (Bad Request))
- jsp: Failed to load resource: the server responded with a status of 400 (Bad Request)
- docker: Error response from daemon: Get https://registry-1.docker.io/v2/: net/http: request canceled
- The installation of Homebrew encountered a 400 Bad Request error
- Error: path not specified when the docker 1.7 file is uploaded to the container in CentOS
- docker Error response from daemon: Bad response from Docker engine
- The docker copies the win10 host file into the docker container. An error is reported: copying between containers is not supported
- Solution of apt unable to update in the docker container of raspberry pie
- Spring MVC error HTTP status 400 – bad request