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.

Sign up for GitHub

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

Jump to bottom

Update docs and other usage of deprecated server.maxPayloadBytes config #97153

Closed
jportner opened this issue Apr 14, 2021 · 2 comments · Fixed by #97158
Closed

Update docs and other usage of deprecated server.maxPayloadBytes config #97153

jportner opened this issue Apr 14, 2021 · 2 comments · Fixed by #97158
Assignees
@jportner
Labels
bug Fixes for quality problems that affect the customer experience docs Team:Core Core services & architecture: plugins, logging, config, saved objects, http, ES client, i18n, etc

Comments

@jportner
Copy link
Contributor

When #95510 was implemented, the server.maxPayloadBytes configuration property was renamed to server.maxPayload.

  • Docs need to be updated to reflect the new property name
  • The kibana.yml file should be updated to reflect the new property name
  • The new property name needs to be added to the allow list for Docker images (src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)
  • Some integration tests need to be updated to use the new property name
@jportner jportner added bug Fixes for quality problems that affect the customer experience docs labels Apr 14, 2021
@botelastic botelastic bot added the needs-team Issues missing a team label label Apr 14, 2021
@jportner jportner added Team:Core Core services & architecture: plugins, logging, config, saved objects, http, ES client, i18n, etc and removed needs-team Issues missing a team label labels Apr 14, 2021
@elasticmachine
Copy link
Contributor

Pinging @elastic/kibana-core (Team:Core)

@jportner
Copy link
Contributor Author

I'm getting ready to submit a PR to add some new config properties for Core to control some security response headers, I'll take care of this while I'm at it.

@jportner jportner self-assigned this Apr 14, 2021
@jportner jportner mentioned this issue Apr 14, 2021
Merged
@jportner jportner linked a pull request Apr 14, 2021 that will close this issue
Add config properties for HTTP security headers #97158
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@jportner jportner

Labels
bug Fixes for quality problems that affect the customer experience docs Team:Core Core services & architecture: plugins, logging, config, saved objects, http, ES client, i18n, etc
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Add config properties for HTTP security headers jportner/kibana
2 participants
@jportner @elasticmachine