fivetran-arunsuri opened a new issue, #2785: URL: https://github.com/apache/polaris/issues/2785
### Is your feature request related to a problem? Please describe. Description: Currently, Polaris API responses do not include a Server header. For example, when performing a POST /api/catalog request, the response headers include only: Content-Type: application/json;charset=UTF-8 content-encoding: gzip content-length: 187 <img width="893" height="369" alt="Image" src="https://github.com/user-attachments/assets/c0bbea9d-dbcc-42bc-bb8f-b4da31f5f962"; /> There is no header identifying the Polaris server or its version. Enhancement Proposal: Add a standard Server header in all HTTP responses from Polaris services. For example: Server: Polaris/1.1.0 Rationale: - Provides better observability and diagnostics during development and debugging. - Allows users and clients to easily verify the server version they’re communicating with, especially across multi-environment or multi-region deployments. - Simplifies support and compatibility checks when interacting with different Polaris API versions. - Aligns with common REST API practices — many Apache and commercial services include Server or custom headers (e.g., X-Server-Version) for version traceability. Optional Consideration: If exposing the server version publicly is a concern for security reasons, a custom header like: X-Polaris-Version: 1.1.0, could be used instead. ### Describe the solution you'd like _No response_ ### Describe alternatives you've considered _No response_ ### Additional context _No response_ -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
