Package: nginx Version: 1.4.1-3 Severity: normal Dear Maintainer,
The Debian config file /etc/nginx/fastcgi_params has the following line fastcgi_param HTTPS $https; But the upstream version of that file (nginx-1.4.1/conf/fastcgi_params) defines that parameter as fastcgi_param HTTPS $https if_not_empty; The difference is that the upstream config will leave HTTPS undefined for plain http connections, while the Debian config will define it as an empty string. I've found this change causes problems with some applications. For example, the CodeIgniter framework assumes https is in use if HTTPS is defined and not equal to 'off'. As far as I can tell, the HTTPS variable was first introduced by Apache mod_ssl, which has the same behavior as the upstream nginx config (defined if https is in use, undefined otherwise). -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.9-1-amd64 (SMP w/4 CPU cores) Locale: LANG=nl_BE.UTF-8, LC_CTYPE=nl_BE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages nginx depends on: ii nginx-full 1.4.1-3 nginx recommends no packages. nginx suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
