-
Notifications
You must be signed in to change notification settings - Fork 2k
Closed as not planned
Labels
backlogPull requests/issues that are backlog itemsPull requests/issues that are backlog itemsbugAn issue reporting a potential bugAn issue reporting a potential bugready for refinementAn issue that was triaged and it is ready to be refinedAn issue that was triaged and it is ready to be refinedstalePull requests/issues with no activityPull requests/issues with no activity
Description
Version
edge
What Kubernetes platforms are you running on?
AKS Azure
Steps to reproduce
When using the client-max-body-size setting in a VirtualServer object in combination with an OIDC policy, the setting is ignored and the default limit of 1MB is applied instead. The restriction appears to originate from the following location https://github.com/nginx/kubernetes-ingress/blob/main/internal/configs/oidc/oidc.conf#L9
We are currently running the latest release of the ingress controller: v5.0.0
Steps to reproduce:
- Create a VirtualServer object with client-max-body-size explicitly set.
- Configure the server to use OIDC.
- Send a request larger than 1MB.
Expected Result:
The request should be accepted if it is within the configured client-max-body-size.
Actual Result:
The request is rejected due to the default 1MB limit, indicating that the custom setting is not being applied.
Metadata
Metadata
Assignees
Labels
backlogPull requests/issues that are backlog itemsPull requests/issues that are backlog itemsbugAn issue reporting a potential bugAn issue reporting a potential bugready for refinementAn issue that was triaged and it is ready to be refinedAn issue that was triaged and it is ready to be refinedstalePull requests/issues with no activityPull requests/issues with no activity
Type
Projects
Status
Done 🚀