boostorg / boostorg/beast

Is `keep_alive` intentionally not implemented for `header`?

Open
#3,041 4 comments 0 reactions 0 assignees View on GitHub
Dominant language
C++
Stars
4.8k
Forks
694
Avg merge
12h 48m
Merged PRs (30d)
1

Description

The `keep_alive` function is implemented for `message` but it only requires information from the `header`. Due to this, any function that composes a response header needs to take the whole `message` unnecessarily.

Our work around is to just re-implement the `keep_alive` function and use that, but I'm wondering if there is a reason I'm missing for the exclusion or whether is just hasn't been a priority to have it in `header`.

Contributor guide

Open the contributing guide

Research direction

The issue names the existing message::keep_alive function and the header data it consumes, but no file or test. Start by locating those APIs and checking current response-header composition callers. Done means determining whether the header should expose equivalent behavior and validating the chosen API behavior.

Written by the indexing model from the issue text.

Assessment

Tech stack
cpp
Domain
backend-api-design, networking
Issue type
Feature
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
38/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.