View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0001035 | savapage-server | [All Projects] General | public | 2019-02-18 19:49 | 2019-08-05 16:41 |
| Reporter | rijkr | Assigned To | rijkr | ||
| Priority | normal | Severity | feature | Reproducibility | N/A |
| Status | closed | Resolution | fixed | ||
| Product Version | 1.0.0 | ||||
| Target Version | 1.1.0 | Fixed in Version | 1.1.0 | ||
| Summary | 0001035: Support X-Forwarded-For (XFF) HTTP header field | ||||
| Description | IST: SavaPage ignores the X-Forwarded-For (XFF) HTTP header field, that is a common method for identifying the originating IP address of a client connecting to a web server through an HTTP proxy or load balancer. So, when SavaPage is shielded by a reverse HTTP proxy each client IP address resolved to 127.0.0.1. SOLL: Add support for (XFF) HTTP header field by adding org.eclipse.jetty.server.ForwardedRequestCustomizer to (both http and https) HttpConfiguration. | ||||
| Additional Information | https://en.wikipedia.org/wiki/X-Forwarded-For | ||||
| Tags | No tags attached. | ||||
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2019-02-18 19:49 | rijkr | New Issue | |
| 2019-02-18 19:49 | rijkr | Status | new => assigned |
| 2019-02-18 19:49 | rijkr | Assigned To | => rijkr |
| 2019-02-18 19:49 | rijkr | Relationship added | related to 0001034 |
| 2019-02-26 10:55 | rijkr | Status | assigned => resolved |
| 2019-02-26 10:55 | rijkr | Resolution | open => fixed |
| 2019-02-26 10:55 | rijkr | Fixed in Version | => 1.1.0 |
| 2019-08-05 16:41 | rijkr | Status | resolved => closed |
| 2019-08-05 16:41 | rijkr | Note Added: 0000168 |
