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

Restore setting of no-cache header in health HTTP responses; add test #9671

Merged
merged 1 commit into from
Jan 21, 2025

Conversation

tjquinno
Copy link
Member

@tjquinno tjquinno commented Jan 20, 2025

Description

Resolves #9670

Release note:


Formerly (in 3.x) HTTP responses from the health endpoint set the Cache-Control header to no-cache, no-store, must-revalidate, no-transform because the returned result could well be different for each request. But 4.x does not do so. This change restores those response header values.


This PR Restores the addition of the no-cache group of headers to the health response that was seemingly accidentally dropped in the move to 4.x.

Adds test checking for the header values.

Documentation

Bug fix. No doc impact.

@tjquinno tjquinno self-assigned this Jan 20, 2025
@oracle-contributor-agreement oracle-contributor-agreement bot added the OCA Verified All contributors have signed the Oracle Contributor Agreement. label Jan 20, 2025
Copy link
Member

@spericas spericas left a comment

Choose a reason for hiding this comment

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

LGTM

@tjquinno tjquinno merged commit c09a47a into helidon-io:main Jan 21, 2025
58 checks passed
@tjquinno tjquinno deleted the 4.x-health-no-cache-fix branch January 21, 2025 15:59
@barchetta barchetta mentioned this pull request Jan 21, 2025
15 tasks
barchetta added a commit that referenced this pull request Feb 10, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
OCA Verified All contributors have signed the Oracle Contributor Agreement.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4.x Health endpoint lost its no-cache settings from 3.x
2 participants