docs: raw bytes are published without a content-type, and how to set one - #3213
Merged
Merged
Conversation
… to set one Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
github-actions
Bot
added
the
documentation
Lancetnik
marked this pull request as ready for review
September 21, 2026 16:56
IvanKirpichnikov
approved these changes
Sep 21, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Split out of #3124.
Adds a section to
getting-started/publishing/index.md: bytes leave the content type empty, how to set one throughheaders=or, for RabbitMQ, thecontent_type=argument, what the consumer sees, and that MQTT has no way to set it.Test plan
just docs-checkon this branch aloneIndependent of the other PRs split from #3124; merges cleanly with each of them.