Skip to content

object: Drop meta headers from PUT chunk requests - #408

Open
cthulhu-rider wants to merge 1 commit into
masterfrom
object-put-chunk-meta-header
Open

object: Drop meta headers from PUT chunk requests#408
cthulhu-rider wants to merge 1 commit into
masterfrom
object-put-chunk-meta-header

Conversation

@cthulhu-rider

Copy link
Copy Markdown
Contributor

No description provided.

Signed-off-by: Leonard Liubich <leonard@morphbits.io>
@cthulhu-rider
cthulhu-rider force-pushed the object-put-chunk-meta-header branch from 8b8605c to 3038602 Compare August 9, 2026 07:54

@roman-khimov roman-khimov left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We can't verify data otherwise. And it's not the biggest problem of PUTs.

@cthulhu-rider

Copy link
Copy Markdown
Contributor Author

We can't verify data otherwise. And it's not the biggest problem of PUTs.

data is verified via verification header

@roman-khimov

Copy link
Copy Markdown
Member

OK, got your point. Repeating meta doesn't make sense, that's true (changing it is also nonsense). So we can do this safely.

@cthulhu-rider
cthulhu-rider marked this pull request as ready for review August 10, 2026 04:59
@roman-khimov

Copy link
Copy Markdown
Member

Thinking about it a bit more I find meta useful for replay attack protection. We currently don't have it, but we should. And the way it should work for chunks is to bind them to a particular stream which can be done using nonce in the first meta message and repeating it in all subsequent ones. In which case version field should be present too. And that makes meta header work as usual for chunks.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants