Uploaded image for project: 'OpenShift Service Mesh'
  1. OpenShift Service Mesh
  2. OSSM-5272

While uploading a file to application pod, Envoy sends 413 request_payload_too_large even though allow_partial_message: true is set

XMLWordPrintable

    • Icon: Ticket Ticket
    • Resolution: Done
    • Icon: Normal Normal
    • None
    • OSSM 2.4.2
    • Maistra
    • None
    • False
    • None
    • False

      Issue: File upload of 10 mB fails when configuring the spec.meshConfig.extensionProviders.envoyExtAuthzHttp.includeRequestBodyInCheck with maxRequestBytes set to 102400000.

      Summary:

      [1] When you configure the SMCP with the following where maxRequestBytes is set to 102400000 which is around 100GB and attempt to upload a file which is around 10 MB the file upload stops at around 1 MB itself.

      extensionProviders:

      • name: "sample-ext-authz-grpc"
        envoyExtAuthzGrpc:
        service: "external-authz-grpc.local"
        port: "9191"
        includeRequestBodyInCheck:
        allowPartialMessage: true
        maxRequestBytes: 102400000
        packAsBytes: true

              mkralik@redhat.com Matej Kralik
              rhn-support-manyayad Mahesh Nyayadhish
              Votes:
              0 Vote for this issue
              Watchers:
              8 Start watching this issue

                Created:
                Updated:
                Resolved: