Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Kibana doesn't seem to honor default 25MB max payload #49218

Closed
n0othing opened this issue Oct 24, 2019 · 2 comments
Closed

Kibana doesn't seem to honor default 25MB max payload #49218

n0othing opened this issue Oct 24, 2019 · 2 comments
Labels
bug Fixes for quality problems that affect the customer experience

Comments

@n0othing
Copy link
Member

n0othing commented Oct 24, 2019

Kibana version: 7.4.1

Elasticsearch version: 7.4.1

Server OS version: n/a

Browser version: Chrome Version 77.0.3865.120 (Official Build) (64-bit)

Browser OS version: macOS Mojave 10.14.6 (18G103)

Original install method (e.g. download page, yum, from source, etc.): tarballs

Describe the bug:

#31974 increased server.maxPayloadBytes to 26214400 (25MB), but I'm unable to save a Markdown Visualization w/ a >1MB payload unless I explicitly set server.maxPayloadBytes: 26214400 in the kibana.yml

Steps to reproduce:

  1. base64 encode a >1MB image (here's one!)
  2. Create a Markdown Visualization and copy/paste the linked base64 image (your browser will likely hang a bit as you try to apply it).
  3. Try to save the visual.

Expected behavior:

The visual's payload is < 25MB, so it should save successfully.

Screenshots (if relevant):

payload too large

Errors in browser console (if relevant):

{"statusCode":413,"error":"Request Entity Too Large","message":"Payload content length greater than maximum allowed: 1048576"}

Any additional context:

Adding server.maxPayloadBytes: 26214400 to the kibana.yml will allow the above visual to successfully save.

@n0othing n0othing added the bug Fixes for quality problems that affect the customer experience label Oct 24, 2019
@kobelb
Copy link
Contributor

kobelb commented Oct 24, 2019

Hey @n0othing, #31974 only bumped up this limit for a specific route which isn't used to save markdown visualizations.

@n0othing
Copy link
Member Author

Ah, I see! I saw #48206 and thought it applied to all routes. Will close.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Fixes for quality problems that affect the customer experience
Projects
None yet
Development

No branches or pull requests

2 participants