handle comments

Author: fivetran-arunsuri

runtime/defaults/src/main/resources/application.properties

@@ -51,15 +51,6 @@ quarkus.http.cors.headers=*
 quarkus.http.cors.exposed-headers=*
 quarkus.http.cors.access-control-max-age=PT10M
 quarkus.http.cors.access-control-allow-credentials=true
-
-# --- Polaris Server header (Quarkus-managed) ---
-# Keep .value present (required by Quarkus), but make the path never match so it's effectively OFF by default.
-quarkus.http.header."Server".value=Polaris/${quarkus.application.version}
-quarkus.http.header."Server".path=/__disabled__
-
-# To enable in production (or any chosen profile), override the path back to normal:
-#%prod.quarkus.http.header."Server".path=/*
-
 quarkus.http.port=8181
 quarkus.http.test-port=0
 

site/content/in-dev/unreleased/configuring-polaris-for-production.md

@@ -128,20 +128,15 @@ in the request.
 ### Polaris Server Header
 
 Polaris can emit an informational `Server` HTTP response header using Quarkus' built-in header
-configuration. The default configuration keeps the header disabled by pointing it at a path that does
-not match any request.
+configuration. Add the following property to one of the supported configuration sources (for example,
+`application.properties`) to enable it with the Polaris version string:
 
 ```properties
 quarkus.http.header."Server".value=Polaris/${quarkus.application.version}
-quarkus.http.header."Server".path=/__disabled__
 ```
 
-To enable the header for production traffic, override the header path for the desired profile (for
-example, `%prod`).
-
-```properties
-%prod.quarkus.http.header."Server".path=/*
-```
+If you prefer to scope the header to specific environments, only set the property for the desired
+profile (for example, `%prod`).
 
 ### Metastore Configuration