"400 Bad Host header" warnings are seen during startup of Live Datamart
Article ID: KB0083909
Updated On:
| Products | Versions |
|---|---|
| TIBCO Live Datamart | 2.1 and earlier |
Description
In some cases, the Live Datamart console produces warnings like the following:
These messages occur because Jetty 9.2 (which ships with Live Datamart 2.1 to act as the web server for web clients) did not support no-value Host for HTTP requests. These messages indicate that the web client has not specified a value for the Host field in the HTTP header. Jetty 9.2 considers this a bad request, but Jetty 9.3 (and later) will allow such requests. For more details, refer to the Jetty defect page.
2017-06-14 09:04:06.649 WARN HttpParser - badMessage: 400 Bad Host header for HttpChannelOverHttp@986fa86{r=0,c=false,a=IDLE,uri=-}
2017-06-14 09:04:08.047 WARN HttpParser - badMessage: 400 Bad Host header for HttpChannelOverHttp@3661d36d{r=0,c=false,a=IDLE,uri=-}
These messages occur because Jetty 9.2 (which ships with Live Datamart 2.1 to act as the web server for web clients) did not support no-value Host for HTTP requests. These messages indicate that the web client has not specified a value for the Host field in the HTTP header. Jetty 9.2 considers this a bad request, but Jetty 9.3 (and later) will allow such requests. For more details, refer to the Jetty defect page.
Issue/Introduction
Warning messages from the HttpParser regarding a bad Host field value are seen during startup of Live Datamart servers (versions 2.1 and earlier)
Resolution
To avoid these warnings, upgrade to Live Datamart 2.2, which ships with Jetty 9.3.
Feedback
Yes
No
Powered by
