tree eda01c379b01140d34e156d5d0776c11e39bd559
parent f8fe53e7114ab10c9059377541277739ace5c1ff
author Gunnar Mills <gmills@us.ibm.com> 1671571127 -0600
committer Ed Tanous <ed@tanous.net> 1671656081 +0000

Return bad request if can't construct

If given a bad URI, e.g. "https://$bmc/?a=id;" return http bad request
(400) like we do other places, e.g. a few lines below.

Certain scanners expect to see bad request when crawling and probing for
vulnerabilities and using not valid URIs. Just dropping the connection
causes errors with these scanners. They think connection problem or
worse the server was taken down.

Tested: Tested downstream https://$bmc/?a=id; returns bad request.

Change-Id: I99a52d4c5e7f366046c5de1cf22c4db95ab39e13
Signed-off-by: Gunnar Mills <gmills@us.ibm.com>