Skip to content

refactor: reorganize and enhance the "Why HTTPS matters" section in c… #256

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.

Sign up for GitHub

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

Merged
IEvangelist merged 1 commit into from
Jan 15, 2026
Merged

refactor: reorganize and enhance the "Why HTTPS matters" section in c… #256

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
26 changes: 12 additions & 14 deletions src/frontend/src/content/docs/app-host/certificate-configuration.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -5,20 +5,6 @@ description: Learn how to configure HTTPS endpoints and certificate trust for re

import { Aside } from '@astrojs/starlight/components';

## Why HTTPS matters

HTTPS is essential for protecting the security and privacy of data transmitted between services. It encrypts traffic to prevent eavesdropping, tampering, and man-in-the-middle attacks. For production environments, HTTPS is a fundamental security requirement.

However, enabling HTTPS during local development to match the production configuration presents unique challenges. Development environments typically use self-signed certificates that browsers and applications don't trust by default. Managing these certificates across multiple services, containers, and different language runtimes can be complex and time-consuming, often creating friction in the development workflow.

Aspire simplifies HTTPS configuration for local development by providing APIs to:

- Configure HTTPS endpoints with appropriate certificates for server authentication
- Manage certificate trust so resources can communicate with services using self-signed certificates
- Automatically handle the .NET provided ASP.NET Core development certificate (a per-user self-signed certificate valid only for local domains) across different resource types

## Overview

Aspire provides two complementary sets of certificate APIs:

1. **HTTPS endpoint APIs**: Configure the certificates that resources use for their own HTTPS endpoints (server authentication)
Expand All @@ -31,6 +17,18 @@ Both sets of APIs work together to enable secure HTTPS communication during loca
included in publish or deployment artifacts.
</Aside>

### Why HTTPS matters
Copy link

Copilot AI Jan 15, 2026

Choose a reason for hiding this comment

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

The "Why HTTPS matters" section is now an H3 heading (###) but appears before any H2 heading in the document. This creates an orphaned subsection that doesn't belong to any parent section. According to proper Markdown document hierarchy, H3 headings should only appear under H2 headings. Consider either keeping it as an H2 heading or creating a parent H2 section for it.

Suggested change
### Why HTTPS matters
## Why HTTPS matters

Copilot uses AI. Check for mistakes.

HTTPS is essential for protecting the security and privacy of data transmitted between services. It encrypts traffic to prevent eavesdropping, tampering, and man-in-the-middle attacks. For production environments, HTTPS is a fundamental security requirement.

However, enabling HTTPS during local development to match the production configuration presents unique challenges. Development environments typically use self-signed certificates that browsers and applications don't trust by default. Managing these certificates across multiple services, containers, and different language runtimes can be complex and time-consuming, often creating friction in the development workflow.

Aspire simplifies HTTPS configuration for local development by providing APIs to:

- Configure HTTPS endpoints with appropriate certificates for server authentication
- Manage certificate trust so resources can communicate with services using self-signed certificates
- Automatically handle the .NET provided ASP.NET Core development certificate (a per-user self-signed certificate valid only for local domains) across different resource types

## HTTPS endpoint configuration

HTTPS endpoint configuration determines which certificate a resource presents when serving HTTPS traffic. This is server-side certificate configuration for resources that host HTTPS/TLS endpoints.
Expand Down
Loading