docs: NGF SNI configuration by sjberman · Pull Request #1764 · nginx/documentation

sjberman · 2026-03-03T15:39:41Z

Proposed changes

Add an include for our HTTPS docs that explains how to handle non-SNI based traffic or disable SNI verification.

Checklist

Before sharing this pull request, I completed the following checklist:

I read the Contributing guidelines
My branch adheres to the Git conventions
My content changes adhere to the F5 NGINX Documentation style guide
If my changes involve potentially sensitive information¹, I have assessed the possible impact
I have waited to ensure my changes pass tests, and addressed any discovered issues

Potentially sensitive information includes personally identify information (PII), authentication credentials, and live URLs. Refer to the style guide for guidance about placeholder content. ↩

Add an include for our HTTPS docs that explains how to handle non-SNI based traffic or disable SNI verification.

sjberman · 2026-03-03T15:39:41Z

Proposed changes

Add an include for our HTTPS docs that explains how to handle non-SNI based traffic or disable SNI verification.

Checklist

Before sharing this pull request, I completed the following checklist:

I read the Contributing guidelines
My branch adheres to the Git conventions
My content changes adhere to the F5 NGINX Documentation style guide
If my changes involve potentially sensitive information¹, I have assessed the possible impact
I have waited to ensure my changes pass tests, and addressed any discovered issues

Potentially sensitive information includes personally identify information (PII), authentication credentials, and live URLs. Refer to the style guide for guidance about placeholder content. ↩

Add an include for our HTTPS docs that explains how to handle non-SNI based traffic or disable SNI verification.

sjberman · 2026-03-03T15:39:41Z

Proposed changes

Add an include for our HTTPS docs that explains how to handle non-SNI based traffic or disable SNI verification.

Checklist

Before sharing this pull request, I completed the following checklist:

I read the Contributing guidelines
My branch adheres to the Git conventions
My content changes adhere to the F5 NGINX Documentation style guide
If my changes involve potentially sensitive information¹, I have assessed the possible impact
I have waited to ensure my changes pass tests, and addressed any discovered issues

Potentially sensitive information includes personally identify information (PII), authentication credentials, and live URLs. Refer to the style guide for guidance about placeholder content. ↩

Add an include for our HTTPS docs that explains how to handle non-SNI based traffic or disable SNI verification.

sjberman · 2026-03-03T15:39:41Z

Proposed changes

Add an include for our HTTPS docs that explains how to handle non-SNI based traffic or disable SNI verification.

Checklist

Before sharing this pull request, I completed the following checklist:

I read the Contributing guidelines
My branch adheres to the Git conventions
My content changes adhere to the F5 NGINX Documentation style guide
If my changes involve potentially sensitive information¹, I have assessed the possible impact
I have waited to ensure my changes pass tests, and addressed any discovered issues

Potentially sensitive information includes personally identify information (PII), authentication credentials, and live URLs. Refer to the style guide for guidance about placeholder content. ↩

Add an include for our HTTPS docs that explains how to handle non-SNI based traffic or disable SNI verification.

sjberman · 2026-03-03T15:39:41Z

Proposed changes

Add an include for our HTTPS docs that explains how to handle non-SNI based traffic or disable SNI verification.

Checklist

Before sharing this pull request, I completed the following checklist:

I read the Contributing guidelines
My branch adheres to the Git conventions
My content changes adhere to the F5 NGINX Documentation style guide
If my changes involve potentially sensitive information¹, I have assessed the possible impact
I have waited to ensure my changes pass tests, and addressed any discovered issues

Potentially sensitive information includes personally identify information (PII), authentication credentials, and live URLs. Refer to the style guide for guidance about placeholder content. ↩

Add an include for our HTTPS docs that explains how to handle non-SNI based traffic or disable SNI verification.

sjberman · 2026-03-03T15:39:41Z

Proposed changes

Add an include for our HTTPS docs that explains how to handle non-SNI based traffic or disable SNI verification.

Checklist

Before sharing this pull request, I completed the following checklist:

I read the Contributing guidelines
My branch adheres to the Git conventions
My content changes adhere to the F5 NGINX Documentation style guide
If my changes involve potentially sensitive information¹, I have assessed the possible impact
I have waited to ensure my changes pass tests, and addressed any discovered issues

Potentially sensitive information includes personally identify information (PII), authentication credentials, and live URLs. Refer to the style guide for guidance about placeholder content. ↩

Add an include for our HTTPS docs that explains how to handle non-SNI based traffic or disable SNI verification.

sjberman · 2026-03-03T15:39:41Z

Proposed changes

Add an include for our HTTPS docs that explains how to handle non-SNI based traffic or disable SNI verification.

Checklist

Before sharing this pull request, I completed the following checklist:

I read the Contributing guidelines
My branch adheres to the Git conventions
My content changes adhere to the F5 NGINX Documentation style guide
If my changes involve potentially sensitive information¹, I have assessed the possible impact
I have waited to ensure my changes pass tests, and addressed any discovered issues

Potentially sensitive information includes personally identify information (PII), authentication credentials, and live URLs. Refer to the style guide for guidance about placeholder content. ↩

Add an include for our HTTPS docs that explains how to handle non-SNI based traffic or disable SNI verification.

sjberman · 2026-03-03T15:39:41Z

Proposed changes

Add an include for our HTTPS docs that explains how to handle non-SNI based traffic or disable SNI verification.

Checklist

Before sharing this pull request, I completed the following checklist:

I read the Contributing guidelines
My branch adheres to the Git conventions
My content changes adhere to the F5 NGINX Documentation style guide
If my changes involve potentially sensitive information¹, I have assessed the possible impact
I have waited to ensure my changes pass tests, and addressed any discovered issues

Potentially sensitive information includes personally identify information (PII), authentication credentials, and live URLs. Refer to the style guide for guidance about placeholder content. ↩

Add an include for our HTTPS docs that explains how to handle non-SNI based traffic or disable SNI verification.

docs: NGF SNI configuration
7c40bd2
Add an include for our HTTPS docs that explains how to handle non-SNI based traffic or disable SNI verification.

sjberman requested review from a team as code owners March 3, 2026 15:39

github-actionsBot added documentation Improvements or additions to documentation product/ngf Issues related to NGINX Gateway Fabric labels Mar 3, 2026

y82 approved these changes Mar 4, 2026
View reviewed changes

sjberman merged commit 853e2da into nginx:ngf-release-2.5Mar 11, 2026
6 checks passed

sjberman deleted the docs/https-sni branch March 11, 2026 14:08

sjberman added a commit that referenced this pull request Mar 27, 2026
docs: NGF SNI configuration (#1764)
259b781
Add an include for our HTTPS docs that explains how to handle non-SNI based traffic or disable SNI verification.

sjberman added a commit that referenced this pull request Mar 30, 2026
docs: NGF SNI configuration (#1764)
6ca1e9c
Add an include for our HTTPS docs that explains how to handle non-SNI based traffic or disable SNI verification.