summaryrefslogtreecommitdiffhomepage
path: root/src/http/modules/ngx_http_scgi_module.c (follow)
AgeCommit message (Collapse)AuthorFilesLines
2012-04-12Fixed grammar in error messages.Ruslan Ermilov1-6/+6
2012-03-15Fixed incorrect ngx_cpystrn() usage in ngx_http_*_process_header().Maxim Dounin1-2/+4
This resulted in a disclosure of previously freed memory if upstream server returned specially crafted response, potentially exposing sensitive information. Reported by Matthew Daley.
2012-03-05Whitespace fixes.Maxim Dounin1-1/+2
2012-01-18Copyright updated.Maxim Konovalov1-0/+1
2012-01-16Fixed proxy_cache_use_stale in "no live upstreams" case.Maxim Dounin1-0/+4
2011-12-26Cache lock support for fastcgi, scgi, uwsgi.Maxim Dounin1-0/+22
2011-12-19Scgi: removed error if there is no Status header.Maxim Dounin1-3/+0
The SCGI specification doesn't specify format of the response, and assuming CGI specs should be used there is no reason to complain. RFC 3875 explicitly states that "A Status header field is optional, and status 200 'OK' is assumed if it is omitted".
2011-12-19Scgi: removed duplicate function declaration.Maxim Dounin1-1/+0
2011-12-19Fixed incorrect use of r->http_version in scgi module.Maxim Dounin1-9/+3
The r->http_version is a version of client's request, and modules must not set it unless they are really willing to downgrade protocol version used for a response (i.e. to HTTP/0.9 if no response headers are available). In neither case r->http_version may be upgraded. The former code downgraded response from HTTP/1.1 to HTTP/1.0 for no reason, causing various problems (see ticket #66). It was also possible that HTTP/0.9 requests were upgraded to HTTP/1.0.
2011-12-09SCGI: added "if_not_empty" flag support to the "scgi_param" directive.Valentin Bartenev1-14/+60
2011-11-16Fixed incorrect counting the length of headers in a SCGI request.Valentin Bartenev1-1/+3
2011-11-14Fixed fastcgi/scgi/uwsgi_param inheritance.Maxim Dounin1-30/+58
The following problems were fixed: 1. Directive fastcgi_cache affected headers sent to backends in unrelated servers / locations (see ticket #45). 2. If-Unmodified-Since, If-Match and If-Range headers were sent to backends if fastcgi_cache was used. 3. Cache-related headers were sent to backends if there were no fastcgi_param directives and fastcgi_cache was used at server level.
2011-11-14Separate functions to merge fastcgi/scgi/uwsgi params.Maxim Dounin1-29/+41
No functional changes.
2011-09-30Added uwsgi_buffering and scgi_buffering directives.Maxim Dounin1-1/+10
Patch by Peter Smit.
2011-08-19Fix ignored headers handling in fastcgi/scgi/uwsgi.Maxim Dounin1-1/+9
The bug had appeared in r3561 (fastcgi), r3638 (scgi), r3567 (uwsgi).
2011-07-29update r3945 with more descriptive error messageIgor Sysoev1-0/+2
2011-04-04fix case when a host in fastcgi_pass, scgi_pass, and uwsgi_passIgor Sysoev1-6/+1
is given by expression and refers to a defined upstream
2010-08-03inherit proxy_pass, fastcgi_pass, uwsgi_pass, scgi_pass insideIgor Sysoev1-0/+8
a limit_except block if no handler was defined for the block
2010-08-02fix directive typeIgor Sysoev1-4/+4
2010-07-19proxy_cache_pass, fastcgi_cache_bypass, uwsgi_cache_bypass, scgi_cache_bypassIgor Sysoev1-0/+11
2010-07-14fix scgi_no_cache and uwsgi_no_cache initializationIgor Sysoev1-0/+1
2010-07-14use ngx_http_test_predicates(), ngx_http_set_predicate_slot()Igor Sysoev1-1/+1
delete ngx_http_cache(), ngx_http_no_cache_set_slot()
2010-07-02do not use a cache headers set to hideIgor Sysoev1-25/+1
2010-07-02update the previous commitIgor Sysoev1-9/+0
2010-07-02use shared ngx_http_upstream_ignore_headers_masks[]Igor Sysoev1-1/+1
2010-06-18ngx_http_scgi_moduleIgor Sysoev1-0/+1674