bryancall commented on code in PR #12947: URL: https://github.com/apache/trafficserver/pull/12947#discussion_r2976787778
########## doc/admin-guide/monitoring/error-messages.en.rst: ########## @@ -108,6 +108,45 @@ it would be used instead of ``cache#read_error`` if there is no ``apache_cache#r The text for an error message is processed as if it were a :ref:`admin-logging-fields` which enables customization by values present in the transaction for which the error occurred. +.. _body-factory-info: + +Template Set Metadata +--------------------- + +Each template set directory must contain a ``.body_factory_info`` file for the template set to be +loaded. This file controls the ``Content-Type``, ``Content-Language``, and character set of the +HTTP response headers sent with error pages. + +The following directives are supported: + +``Content-Language`` + The natural language of the error pages. This value is sent in the ``Content-Language`` HTTP + response header. Default: ``en``. + +``Content-Charset`` + The character encoding of the error pages. This value is appended to the ``Content-Type`` header + as a ``charset`` parameter. Default: ``utf-8``. + +``Content-Type`` + The MIME type for the error response. This controls the media type portion of the ``Content-Type`` + HTTP response header. Default: ``text/html``. + +For example, to serve plain text error pages in English:: + + Content-Language: en + Content-Charset: utf-8 + Content-Type: text/plain + +This would produce the response header ``Content-Type: text/plain; charset=utf-8``. + +To describe Korean error pages encoded in the ``iso-2022-kr`` character set:: + + Content-Language: kr Review Comment: Good call. Updated both the admin-guide example and the shipped `.body_factory_info` comment example to use `Content-Language: ko-KR` in `05229021f5`. -- 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]
