Skip to content

waf/ update security update doc#2033

Open
dkleinF5 wants to merge 2 commits into
mainfrom
waf/security-update-command
Open

waf/ update security update doc#2033
dkleinF5 wants to merge 2 commits into
mainfrom
waf/security-update-command

Conversation

@dkleinF5
Copy link
Copy Markdown
Contributor

@dkleinF5 dkleinF5 commented Jun 4, 2026

Proposed changes

Checklist

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

Footnotes

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

@dkleinF5 dkleinF5 requested a review from a team as a code owner June 4, 2026 20:20
@github-actions github-actions Bot added documentation Improvements or additions to documentation product/waf Issues related to F5 WAF for NGINX labels Jun 4, 2026
@github-actions
Copy link
Copy Markdown

github-actions Bot commented Jun 4, 2026

Deploy Preview will be available once build job completes!

Name Link
😎 Deploy Preview https://frontdoor-test-docs.nginx.com/previews/docs/2033/

Copy link
Copy Markdown
Contributor

@mjang mjang left a comment

Choose a reason for hiding this comment

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

Good info. And it's clear that you're differentiating between reload and restart


## Apply the updated signatures

Updated signatures don't take effect until you reload NGINX. Until you reload, F5 WAF for NGINX keeps running the previous signatures.
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

I think this paragraph and the next could be improved. The first 2 sentences are a bit redundant

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

@JTorreG is this change better "Updated signatures take effect after you reload NGINX. Until then, F5 WAF for NGINX keeps running the previous signatures."?

Copy link
Copy Markdown
Contributor

@JTorreG JTorreG left a comment

Choose a reason for hiding this comment

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

Nits


- `nginx -s reload`
- `sudo systemctl reload nginx`
- On all platforms: `nginx -s reload`
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Al platforms or all except the ones in the next step?

For the ones in the next step are both commands necessary?

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

Does this change clarify things?

  • On all platforms: nginx -s reload
  • On systemd-based platforms (Amazon Linux, Debian, Oracle Linux, RHEL, Rocky Linux, Ubuntu), you can reload NGINX with: sudo systemctl reload nginx instead

@ohad-perets
Copy link
Copy Markdown
Contributor

What about when the user upgrades signatures in the compiler image?

@dkleinF5 dkleinF5 requested a review from JTorreG June 8, 2026 05:16
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

documentation Improvements or additions to documentation product/waf Issues related to F5 WAF for NGINX

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants