Back to bug 1298571
| Who | When | What | Removed | Added |
|---|---|---|---|---|
| Neil Levine | 2016-01-20 14:48:37 UTC | CC | nlevine | |
| Pete Zaitcev | 2016-01-20 17:11:24 UTC | CC | zaitcev | |
| Neil Levine | 2016-02-11 00:58:19 UTC | Summary | Civetweb Does Not Have Cache Control Header or Custom Logging Headers | [RFE] Log X-Forwarded-For information |
| Matt Benjamin (redhat) | 2016-05-03 17:42:46 UTC | Status | NEW | ASSIGNED |
| Assignee | yehuda | mbenjamin | ||
| Benjamin Schmaus | 2016-05-11 13:40:21 UTC | Flags | needinfo?(mbenjamin) | |
| Matt Benjamin (redhat) | 2016-05-11 13:52:48 UTC | Flags | needinfo?(mbenjamin) | |
| Ken Dreyer (Red Hat) | 2016-08-03 19:27:26 UTC | Target Release | 1.3.3 | 1.3.4 |
| CC | kdreyer | |||
| chrone | 2016-11-19 02:05:53 UTC | CC | charlesalva | |
| Matt Benjamin (redhat) | 2017-01-12 21:11:26 UTC | Status | ASSIGNED | POST |
| Target Release | 1.3.4 | 2.2 | ||
| shilpa | 2017-01-13 07:27:12 UTC | CC | smanjara | |
| Flags | needinfo?(mbenjamin) | |||
| Harish NV Rao | 2017-01-17 12:09:50 UTC | CC | hnallurv | |
| Flags | needinfo?(mbenjamin) | |||
| Matt Benjamin (redhat) | 2017-01-17 12:24:17 UTC | Flags | needinfo?(mbenjamin) needinfo?(mbenjamin) | |
| Harish NV Rao | 2017-01-19 12:28:35 UTC | QA Contact | ceph-qe-bugs | smanjara |
| Ken Dreyer (Red Hat) | 2017-01-20 23:42:47 UTC | Status | POST | MODIFIED |
| Fixed In Version | RHEL: ceph-10.2.5-7.el7cp Ubuntu: ceph_10.2.5-3redhat1xenial | |||
| errata-xmlrpc | 2017-01-20 23:50:17 UTC | Status | MODIFIED | ON_QA |
| Harish NV Rao | 2017-02-09 14:28:14 UTC | QA Contact | smanjara | rperiyas |
| John Poelstra | 2017-02-15 15:10:39 UTC | Doc Text | Feature: Reason: Result: .. | |
| Doc Type | Bug Fix | Enhancement | ||
| Ramakrishnan Periyasamy | 2017-02-17 09:12:17 UTC | Status | ON_QA | VERIFIED |
| Bara Ancincova | 2017-02-21 12:19:32 UTC | Blocks | 1412948 | |
| Docs Contact | bancinco | |||
| Matt Benjamin (redhat) | 2017-02-21 18:36:46 UTC | Doc Text | Feature: Reason: Result: .. | .Custom HTTP header logging has been added to Ceph Object Gateway Sites using the Civetweb HTTP front-end previously lacked the ability to log custom HTTP headers, as they could when using Apache and FCGI. To log custom HTTP headers, first enable the os log socket on the gateway instance, by setting "rgw enable ops log = true" and specifying an ops log socket path ("rgw ops log socket path = <path>") in ceph.conf. Then to log specific HTTP headers, list those headers as a quoted, comma-separated list as the value of the "rgw log http headers" option in ceph.conf (e.g., rgw log http headers = "http_x_forwarded_for, http_expect, http_content_md5"). When these options are enabled, observed headers matching the desired header list are provided as a json-formatted key-value list with the key "http_x_headers" in the ops log stream. |
| Matt Benjamin (redhat) | 2017-02-21 18:38:05 UTC | Doc Text | .Custom HTTP header logging has been added to Ceph Object Gateway Sites using the Civetweb HTTP front-end previously lacked the ability to log custom HTTP headers, as they could when using Apache and FCGI. To log custom HTTP headers, first enable the os log socket on the gateway instance, by setting "rgw enable ops log = true" and specifying an ops log socket path ("rgw ops log socket path = <path>") in ceph.conf. Then to log specific HTTP headers, list those headers as a quoted, comma-separated list as the value of the "rgw log http headers" option in ceph.conf (e.g., rgw log http headers = "http_x_forwarded_for, http_expect, http_content_md5"). When these options are enabled, observed headers matching the desired header list are provided as a json-formatted key-value list with the key "http_x_headers" in the ops log stream. | .Custom HTTP header logging has been added to Ceph Object Gateway Sites using the Civetweb HTTP front-end previously lacked the ability to log custom HTTP headers, as they could when using Apache and FCGI. To log custom HTTP headers, first enable the ops log socket on the gateway instance, by setting "rgw enable ops log = true" and specifying an ops log socket path ("rgw ops log socket path = <path>") in ceph.conf. Then to log specific HTTP headers, list those headers as a quoted, comma-separated list as the value of the "rgw log http headers" option in ceph.conf (e.g., rgw log http headers = "http_x_forwarded_for, http_expect, http_content_md5"). When these options are enabled, observed headers matching the desired header list are provided as a json-formatted key-value list with the key "http_x_headers" in the ops log stream. |
| Bara Ancincova | 2017-02-23 13:39:32 UTC | Doc Text | .Custom HTTP header logging has been added to Ceph Object Gateway Sites using the Civetweb HTTP front-end previously lacked the ability to log custom HTTP headers, as they could when using Apache and FCGI. To log custom HTTP headers, first enable the ops log socket on the gateway instance, by setting "rgw enable ops log = true" and specifying an ops log socket path ("rgw ops log socket path = <path>") in ceph.conf. Then to log specific HTTP headers, list those headers as a quoted, comma-separated list as the value of the "rgw log http headers" option in ceph.conf (e.g., rgw log http headers = "http_x_forwarded_for, http_expect, http_content_md5"). When these options are enabled, observed headers matching the desired header list are provided as a json-formatted key-value list with the key "http_x_headers" in the ops log stream. | .The Ceph Object Gateway now supports custom HTTP header logging Sites that use the Civetweb HTTP web server previously lacked the ability to log custom HTTP headers, as they could when using the Apache web server and the FastCGI protocol. With this update, the Ceph Object Gateway supports custom HTTP header logging. To log custom HTTP headers, enable the operations log socket on the Ceph Object Gateway instance and list the HTTP headers. Add the following parameters to the Ceph configuration file: ---- rgw enable ops log = true rgw ops log socket path = <path> rgw log http headers = "<headers>" ---- Replace `<path>` with the path to the operations log socket and `<headers` with a comma-separated list of custom HTTP headers, for example: ---- rgw enable ops log = true rgw ops log socket path = /tmp/opslog rgw log http headers = "http_x_forwarded_for, http_expect, http_content_md5" ---- The operations log stream then lists the headers as a JSON-formatted key-value list with the "http_x_headers" key. |
| Flags | needinfo?(mbenjamin) | |||
| Matt Benjamin (redhat) | 2017-02-23 13:44:41 UTC | Flags | needinfo?(mbenjamin) | |
| errata-xmlrpc | 2017-03-13 11:56:13 UTC | Status | VERIFIED | RELEASE_PENDING |
| errata-xmlrpc | 2017-03-14 15:43:36 UTC | Status | RELEASE_PENDING | CLOSED |
| Resolution | --- | ERRATA | ||
| Last Closed | 2017-03-14 11:43:36 UTC | |||
| Drew Harris | 2017-07-30 15:47:47 UTC | Sub Component | RGW | |
| CC | cbodley, kbader | |||
| Component | Ceph | RGW | ||
| Vikhyat Umrao | 2018-09-13 22:30:23 UTC | CC | vumrao | |
| Vikhyat Umrao | 2018-09-13 22:31:46 UTC | Link ID | Red Hat Knowledge Base (Solution) 3613291 |
Back to bug 1298571