In a production environment, or because the url is too long results in a return header 400
at this time there are two options
Option One
The maximum increase in the container header length
tomcat
server:
tomcat:
max-http-header-size: 16000
uri-encoding: UTF-8
max-http-header-size: 16000
jetty
server:
max-http-header-size: 16000
undertow
server:
max-http-header-size: 16000
If there is a gateway or ng need to be adjusted in response to the header
Option II
Reduce unnecessary header, and the header compression
often need to pass through some of the parameters in the header during the call feign, many people may convenience will pass through all the header, this can lead to several problems,
1, header excessive
2, causing some network services declined because many of the services configured security whitelist and the like, and so need to check host, if the host could lead to pass through the check is not passed.
