Web Server Configuration Review
Check headers, TLS and routing rules.
The Open buttons send the prompt text as currently shown below to that site only when you click. Fill in the placeholders first.
[VERIFY] is an editorial flag, not a blank to fill. Wherever the prompt shows [VERIFY], check that item against a reliable source before you use it.
Review a web server configuration. Paste the server blocks or config with secrets removed: [SERVER_CONFIG]. What sits behind it: [BACKENDS]. Clients: [CLIENTS]. Check TLS settings, redirects, security headers, caching rules, request size and timeout limits, access to hidden files, directory listings, logging, and rules that expose internal paths. Explain what each setting does. Return a table with Directive, Issue, Severity (red, amber, green) and Fix, a corrected snippet, and a test list using harmless requests on a staging copy. Also suggest how to back up the current configuration before changes, how to reload without dropping connections, and how to monitor error rates after the change. Add a short list of settings that differ between staging and production and why. Keep this defensive and for systems I own or am authorised to review. Do not provide exploit code, attack steps or ways to evade detection, and tag any legal or disclosure question [VERIFY] for [JURISDICTION].
Fill in before use
Optional: type your details and the prompt above updates. Nothing is saved or sent.
Replace each bracketed placeholder with your own details, then paste into Any AI or another assistant.