SAP Knowledge Base Article - Preview

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 the BEx Broadcaster is called from BEx Web Analyzer, you might experience the error 400 Bad HTTP request error, a blank internet explorer window or the BEx Web Analyzer starts instead of BEx Broadcaster.

2 (1).png       Issue 2.png      Issue 3.png

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



Business Information Warehouse    -   Release Independent


SAP NetWeaver all versions


Blank, BEx Broadcaster, BEx Web Analyzer, 400 Bad HTTP request, Error, 972514, POST, GET, iView, empty, blank, request method , KBA , BW-BEX-ET-BC , Broadcasting , BW-BEX-ET-WJR , BEx Web Java Runtime , BW-BEX-ET-WJR-RT , Web Runtime and API commands , Problem

About this page

This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP for Me (Login required).

Search for additional results

Visit SAP Support Portal's SAP Notes and KBA Search.