public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: [PATCH 1/4] httpd: remove compatibility instructions for very old browsers
Date: Wed, 14 Apr 2021 18:24:20 +0100	[thread overview]
Message-ID: <35BCF0DE-1BB1-41EE-8ACA-4E9EA6A0DE75@ipfire.org> (raw)
In-Reply-To: <0b270dd5-9a61-2901-c75e-8698dd4373e8@ipfire.org>

[-- Attachment #1: Type: text/plain, Size: 1760 bytes --]

Thank you. Excellent work.

> On 12 Apr 2021, at 22:00, Peter Müller <peter.mueller(a)ipfire.org> wrote:
> 
> These are not in use any more - and if they would, we don't support them.
> 
> Signed-off-by: Peter Müller <peter.mueller(a)ipfire.org>
> ---
> config/httpd/server-tuning.conf                 | 10 ----------
> config/httpd/vhosts.d/ipfire-interface-ssl.conf |  3 ---
> 2 files changed, 13 deletions(-)
> 
> diff --git a/config/httpd/server-tuning.conf b/config/httpd/server-tuning.conf
> index 5642a1e44..9ee651e45 100644
> --- a/config/httpd/server-tuning.conf
> +++ b/config/httpd/server-tuning.conf
> @@ -22,13 +22,3 @@ MaxSpareThreads 20
> StartServers 2
> MaxRequestWorkers 256
> ThreadsPerChild 16
> -
> -#
> -# The following directives modify normal HTTP response behavior to
> -# handle known problems with browser implementations.
> -#
> -BrowserMatch "Mozilla/2" nokeepalive
> -BrowserMatch "MSIE 4\.0b2;" nokeepalive downgrade-1.0 force-response-1.0
> -BrowserMatch "RealPlayer 4\.0" force-response-1.0
> -BrowserMatch "Java/1\.0" force-response-1.0
> -BrowserMatch "JDK/1\.0" force-response-1.0
> diff --git a/config/httpd/vhosts.d/ipfire-interface-ssl.conf b/config/httpd/vhosts.d/ipfire-interface-ssl.conf
> index de7b8559d..8c4cf3806 100644
> --- a/config/httpd/vhosts.d/ipfire-interface-ssl.conf
> +++ b/config/httpd/vhosts.d/ipfire-interface-ssl.conf
> @@ -64,9 +64,6 @@
> 	SSLOptions +StdEnvVars
>     </Directory>
>     SetEnv HOME /home/nobody
> -    SetEnvIf User-Agent ".*MSIE.*" \
> -	nokeepalive ssl-unclean-shutdown \
> -	downgrade-1.0 force-response-1.0
>     CustomLog /var/log/httpd/ssl_request_log \
> 	"%t %h %{SSL_PROTOCOL}x %{SSL_CIPHER}x \"%r\" %b"
> 
> -- 
> 2.26.2


      parent reply	other threads:[~2021-04-14 17:24 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-12 21:00 Peter Müller
2021-04-12 21:00 ` [PATCH 2/4] httpd: disable sending ETag header completely Peter Müller
2021-04-12 21:01   ` [PATCH 3/4] httpd: apply the same security headers on the captive portal instance as we do elsewhere Peter Müller
2021-04-12 21:01     ` [PATCH 4/4] httpd: delete comment blocks and unused directives from our configuration Peter Müller
2021-04-14 17:24 ` Michael Tremer [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=35BCF0DE-1BB1-41EE-8ACA-4E9EA6A0DE75@ipfire.org \
    --to=michael.tremer@ipfire.org \
    --cc=development@lists.ipfire.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox