SAP Knowledge Base Article - Preview

3632639 - HTTP 400 Request header or Cookie too large Error on Cloud Foundry tied to NGIX Server and over 150 roles per user

Symptom

  • An HTTP 400 Error is received from the Cloud Foundry when a User connecting to it, has over 150 roles.
    • However, if the user only has 1 to 100 roles, it is successful.
    • What is seen on connecting to the Cloud with NGIX server is that at 150+ roles, the HTTP Request is TOO LONG and the backend cannot process it.
  • When the company assigns a user with over 150 roles, there is a security response from the backend that shows:
    • "HTTP 400 Error - Bad Request : Request header or Cookie too large" occurs on nginx when accessing to an app in SAP BTP.
      • The application is build on app router provided by SAP, node js, and java.
      • The app is not using nginx.
      • What is observed: nginx web server is being used internally in SAP BTP cloud foundry environment.
      • This error occurs only when many role collections (more than 150) are assigned to a user.
        • The error does not occur when user whom some role collections are assigned to access the app.
  • What can be done to resolve this type of issue?


Read more...

Environment

  • BTP
  • Cloud Integration
  • SAP Business Technology Platform

Product

BTP all versions ; Cloud Integration all versions ; SAP Business Technology Platform all versions

Keywords

Angular, HTTP 400 Error, HTTP 400 Cloud Foundry, Multiple Roles per user, Over 100 roles for a user, HTTP header limitation, HTTP Header Size, NGINX web servers, HTTP Maximum Header Size, S/4HANA Servers Header , KBA , BC-CP-CF , Cloud Foundry , BC-CST-IC , Internet Communication Manager , CEC-SPA , SAP Commerce Cloud Spartacus , CEC-SCC-COM-SEDIT , SmartEdit , 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.