https://bz.apache.org/bugzilla/show_bug.cgi?id=63852
--- Comment #16 from Christopher Schultz <ch...@christopherschultz.net> ---
(In reply to Mark Thomas from comment #14)
> I'm leaning towards resolving this as WONTFIX.
+1
> The server attribute defaults to null whereas ServerInfo (as used in the
> ErrorReportValve and other places) defaults to "Apache Tomcat/<version>".
Similar to the (ahem) HTTP status reason phrase, these things serve two
different use-cases: one of them -- the "Server" response header -- is intended
to be read by client software and used for decision making, statistics, etc.
The other -- the footer of error pages -- is intended to be read by humans.
(In reply to Konstantin Kolinko from comment #15)
> If server.info property of ServerInfo.properties file were exposed as a
> system property (maybe by a custom PropertySource), one could write
> <Connector server="${server.info}"> to have the same value as displayed by
> ErrorReportValve. But actually I think that nobody wants such feature.
This would kind of be the best way to do this. It allows you to at least
configure the value in a single place and have it "copied" around to the other
places, if that's what you want. But ... really, this isn't that big of a deal.
> (The attribute "server" on a Connector is a protocol option for HTTP/1.1 for
> one the headers defined by that protocol. It is a wrong place to define a
> server-wide value. The Connector for AJP protocol [3] does not have such
> option.)
But it's not a server-wide value. The AJP connector doesn't have it because by
definition it's being used by a proxy. The proxy supplies its own "Server"
header.
--
You are receiving this mail because:
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org
