typing error in default-ssl

Bug #626728 reported by Lukas Zronek on 2010-08-30
This bug affects 2 people
Affects Status Importance Assigned to Milestone
apache2 (Ubuntu)

Bug Description

Binary package hint: apache2

There is a typing error in the file /etc/apache2/sites-available/default-ssl on line 169:

BrowserMatch "MSIE [17-9]" ssl-unclean-shutdown

should be

BrowserMatch "MSIE [7-9]" ssl-unclean-shutdown


Release: Ubuntu 10.04.1 LTS
Package: apache2.2-common

  Installed: 2.2.14-5ubuntu8
  Candidate: 2.2.14-5ubuntu8
  Version table:
 *** 2.2.14-5ubuntu8 0
        500 http://at.archive.ubuntu.com/ubuntu/ lucid/main Packages
        100 /var/lib/dpkg/status

Lukas Zronek (lukas-z) wrote :
Chuck Short (zulcss) wrote :

Thanks for catching this. Ill make sure it gets into maverick.


Changed in apache2 (Ubuntu):
importance: Undecided → Medium
status: New → Triaged
Stefan Fritsch (sf-sfritsch) wrote :

This is intentional, the regexp is supposed to match MSIE 10 and up. The probability that someone still uses MSIE 1 is zero, but MSIE 10 is not that far away.

tags: added: patch
Changed in apache2 (Ubuntu):
status: Triaged → Invalid
Lukas Zronek (lukas-z) wrote :

@Stefan Fritsch: Maybe you didn't see the whole thing. The first BrowserMatch is supposed to match MSIE 2-6 and the second should match "MSIE 7 and newer" according to the comment on line 168.


    165 BrowserMatch "MSIE [2-6]" \
    166 nokeepalive ssl-unclean-shutdown \
    167 downgrade-1.0 force-response-1.0
    168 # MSIE 7 and newer should be able to use keepalive
    169 BrowserMatch "MSIE [17-9]" ssl-unclean-shutdown

Stefan Fritsch (sf-sfritsch) wrote :

Luka, that's correct. "MSIE [17-9]" matches MSIE 7 to 9 and 10 to 19 (and 1, but that should not be a problem).

Cd-MaN (x-at-y-or-z) wrote :

While this regex works (kind of - it also matches MSIE 1, but that should be a negligable minority) I would like to propose the following regex which is clearer (imho):

BrowserMatch "MSIE (?:[7-9]|\d{2,})" ssl-unclean-shutdown

Alex (normadize) wrote :

This bug still exists today (2.4.18)

Alex (normadize) wrote :

Apologies, wrong bug (please delete/ignore my posts here)

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers