developer.jelix.org is not used any more and exists only for
history. Post new tickets on the Github account.
developer.jelix.org n'est plus utilisée, et existe uniquement pour son historique. Postez les nouveaux tickets sur le compte github.
developer.jelix.org n'est plus utilisée, et existe uniquement pour son historique. Postez les nouveaux tickets sur le compte github.
Opened 9 years ago
Closed 9 years ago
#1411 closed enhancement (fixed)
Add a config option to force HTTP version
Reported by: | bricet | Owned by: | laurentj |
---|---|---|---|
Priority: | normal | Milestone: | Jelix 1.3 |
Component: | jelix:core response | Version: | trunk |
Severity: | normal | Keywords: | http version nginx |
Cc: | Blocked By: | ||
Blocking: | Documentation needed: | no | |
Hosting Provider: | Php version: |
Description
In some cases, it would be convenient to be able to specify HTTP version in answers.
In my case, this is usefull when using Nginx as a reverse proxy (see http://wiki.nginx.org/HttpProxyModule) : when not forcing to HTTP 1.0, this can lead to troubles when having nginx + gzipping on large pages.
Here is a patch to do that.
Attachments (1)
Change History (5)
Changed 9 years ago by bricet
comment:1 Changed 9 years ago by bricet
- review set to review?
comment:2 Changed 9 years ago by bricet
comment:3 Changed 9 years ago by laurentj
- Component changed from jelix to jelix:core response
- Milestone set to Jelix 1.3
- Owner set to laurentj
- review changed from review? to review+
comment:4 Changed 9 years ago by laurentj
- Resolution set to fixed
- Status changed from new to closed
landed. thanks :)
https://bitbucket.org/jelix/jelix-trunk/changeset/835d188c23a4
Note: See
TracTickets for help on using
tickets.
Epic fail on patch filename ... bug its content should be OK, though ...