#11793 closed defect (fixed)
FCGI gateway does not adequately detect URL scheme
| Reported by: | ccm | Owned by: | chaz |
|---|---|---|---|
| Priority: | normal | Milestone: | 1.0.5 |
| Component: | web frontend | Version: | 1.0.1 |
| Severity: | normal | Keywords: | fcgi patch proxy |
| Cc: | Branch: | ||
| Release Notes: |
Handle |
||
| API Changes: | |||
| Internal Changes: | |||
Description
Unlike the WSGI gateway, the FCGI gateway's HTTPS detection is inadequate. Here's a patch the fixes the issue by copying the relevant code from trac/web/wsgi.py to trac/web/_fcgi.py.
Attachments (1)
Change History (8)
by , 11 years ago
| Attachment: | 0001-Try-harder-to-detect-the-correct-URL-scheme.patch added |
|---|
comment:1 by , 11 years ago
comment:2 by , 11 years ago
| Milestone: | → 1.0.4 |
|---|
This looks reasonable. For reference the existing wsgi.py code got the HTTP_X_FORWARDED_PROTO check in #8131 for WSGI. (Other than that both the initial FCGI ([2130]) and WSGI ([2957]) HTTPS detection remain unchanged.)
comment:3 by , 11 years ago
| Milestone: | 1.0.4 → 1.0.5 |
|---|
comment:4 by , 11 years ago
| Keywords: | proxy added |
|---|
comment:5 by , 11 years ago
Yeah. I think no problems here. It would be good to handle HTTP_X_FORWARDED_PROTO in _fcgi.py.
comment:6 by , 11 years ago
| Release Notes: | modified (diff) |
|---|---|
| Resolution: | → fixed |
| Status: | new → closed |
comment:7 by , 11 years ago
| Owner: | set to |
|---|



As an example, the FCGI gateway currently will set
wsgi.url_schemetohttpsifHTTPSin the environment isonbut not if it isON(all caps).