1921802 - 400 Bad HTTP request Error / Request-URI too large

"Image/data in this KBA is from SAP internal systems, sample data, or demo systems. Any resemblance to real data is purely coincidental." 

When invoking the BEx Broadcaster from the BEx Web Analyzer, you may encounter issues, such as a "400 Bad HTTP Request" error, a blank browser (Internet Explorer, MS Edge, Chrome, ...)  window, or an unexpected launch of the BEx Web Analyzer instead of the BEx Broadcaster.

Several other issues like error HTTP Error 403, 404, 401, 414  could appear, instead of the screenshots above. SAP still not predicted all of them, but consider to implement this note if the BEx Broadcaster behaves incorrectly.
Possible issues:

• 400 Bad Request,
• 401 Unauthorized
• 403 Forbidden
• 404 Not Found
• 406 Not Acceptable
• 414 URI Too Long
• 431 Request Header Fields Too Large
• 500 Internal Server Error
• 502 Bad Gateway
• 503 Service Unavailable
• 501 Not Implemented

Blank, BEx Broadcaster, BEx Web Analyzer, 400 Bad HTTP request, Error, 972514, POST, GET, iView, empty, blank page, request method, Changing GET to POST, URL length, Server request size limit, large url, , KBA , BW-BEX-ET-BC , Broadcasting , BW-BEX-ET-WJR , BEx Web Java Runtime , BW-BEX-ET-WJR-RT , Web Runtime and API commands , BW-BEX-ET-BC-EP , Portalintegration, Export to the Portal , BW-BEX-ET-BC-MAIL , Broadcasting Mailing , Problem