aMule Bug Tracker - aMule | |||||
| View Issue Details | |||||
| ID | Project | Category | View Status | Date Submitted | Last Update |
| 0001756 | aMule | Utilities | public | 2015-08-04 20:12 | 2015-10-16 12:27 |
| Reporter | circulosmeos | ||||
| Assigned To | |||||
| Priority | normal | Severity | minor | Reproducibility | always |
| Status | resolved | Resolution | fixed | ||
| Platform | OS | OS Version | |||
| Product Version | 2.3.1 | ||||
| Target Version | Fixed in Version | 2.3.2 | |||
| Fixed in Revision | |||||
| Operating System | Any | ||||
| Summary | 0001756: amuleweb: HTTP headers are case insensitive | ||||
| Description | Using amuleweb: If "cookie: " HTTP header is not read (instead of "Cookie: "), and amuleweb is accessed via a proxy or web browser that writes HTTP headers as low case, amuleweb is rendered unusable. Problem is that with the advent of http/2 any proxy can (and will) rewrite http headers as low case. | ||||
| Steps To Reproduce | Configuring a reverse proxy with a nginx compiled with SPDY (~http/2) support. Reverse proxies can be useful to group or hide these services' webs behind a common port, or other uses. | ||||
| Additional Information | I've issued a (very tentative) pull request on github repository: https://github.com/gonosztopi/amule/pull/1 [^] Long explanation of this issue: http://wp.me/p2FmmK-8r [^] | ||||
| Tags | No tags attached. | ||||
| Relationships | |||||
| Attached Files | |||||
| Issue History | |||||
| Date Modified | Username | Field | Change | ||
| 2015-08-04 20:12 | circulosmeos | New Issue | |||
| 2015-10-16 12:27 | GonoszTopi | Status | new => resolved | ||
| 2015-10-16 12:27 | GonoszTopi | Resolution | open => fixed | ||
| 2015-10-16 12:27 | GonoszTopi | Fixed in Version | => 2.3.2 | ||
| There are no notes attached to this issue. |