Bad HTTP Status 400
Information
| Summary: |
Failing health checks due to Bad HTTP status 400. |
| Environment: |
Product: LoadMaster Version: Any Platform: Any Application: Any |
| Question/Problem Description: |
|
| Steps to Reproduce: | |
| Error Message: | Bad HTTP status 400 from <Real Server IP> |
| Defect Number: | |
| Enhancement Number: | |
| Cause: | The SNI Hostname needs to be specified on the LoadMaster. |
| Resolution: |
Specify the SNI Hostname within the health check parameters. Navigate to the virtual service and expand the Real Servers tab. Enable Use HTTP/1.1 and specify the SNI Hostname within the HTTP/1.1 Host field. If the virtual service is re-encrypting traffic additional changes are needed within SSL Preoperties. Pass through SNI hostname can be enabled to pass along the SNI Hostname from the client to the server. Reencryption SNI Hostname can also be used to specify which hostname to append to the client connection. If you are unsure where to find the SNI Hostname of the server, this can be found within the real servers site bindings. |
| Workaround: | |
| Notes: |
https://support.kemptechnologies.com/hc/en-us/articles/10125740085773 https://support.kemptechnologies.com/hc/en-us/articles/6914490937613-Bad-HTTP-status-received-503 |