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

Change info endpoint to be secure and unexposed by default #24533

Closed
philwebb opened this issue Dec 16, 2020 · 1 comment
Closed

Change info endpoint to be secure and unexposed by default #24533

philwebb opened this issue Dec 16, 2020 · 1 comment
Labels
type: enhancement A general enhancement

Comments

@philwebb
Copy link
Member

This issue is to continue the discussion started in #24205

@philwebb philwebb added for: team-meeting An issue we'd like to discuss as a team to make progress status: waiting-for-triage An issue we've not yet triaged labels Dec 16, 2020
@philwebb philwebb changed the title Consider if info endpoint should be secure and/or unexposed by default Consider if info endpoint should be secure and unexposed by default Dec 18, 2020
@philwebb philwebb added type: enhancement A general enhancement and removed for: team-meeting An issue we'd like to discuss as a team to make progress status: waiting-for-triage An issue we've not yet triaged labels Dec 18, 2020
@philwebb philwebb added this to the 2.5.x milestone Dec 18, 2020
@philwebb philwebb changed the title Consider if info endpoint should be secure and unexposed by default Change info endpoint to be secure and unexposed by default Dec 18, 2020
@mbhave
Copy link
Contributor

mbhave commented Jan 14, 2021

Closing in favor of PR #24715.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type: enhancement A general enhancement
Projects
None yet
Development

No branches or pull requests

2 participants