Large cookies should return 431, not 400

[Stono]

Hi,
Recently we were debugging an issue with a large cookie with @aledbf which was returning a 400 from nginx. It feels like 431 is a more appropriate code.

We resolved the issue by setting:

  large-client-header-buffers: "4 16k"
  client-header-buffer-size: 2k

https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/431

/kind bug

[aledbf]

@Stono please check #4593

[Stono]

hey @aledbf - i'm not sure how that issue helps me? Am I missing something?

[aledbf]

Relevant links:

• http://mailman.nginx.org/pipermail/nginx/2018-June/056342.html
• https://www.nginx.com/resources/wiki/extending/api/http/
• https://forum.nginx.org/read.php?2,286897,286912#msg-286912

Not sure what implies handling error_page 494 =XXX in the template.

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

[fejta-bot]

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle rotten

[fejta-bot]

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close

[k8s-ci-robot]

@fejta-bot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.