More information is available at http://httpd.apache.org/docs-project/ Contents 1 Release Notes 1 1.1 Upgrading to 2.0 from 1.3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 663 viii CONTENTS Chapter 1 Release Notes 1 2 CHAPTER 1. RELEASE NOTES 1.1 Upgrading to 2.0 from 1.3 In order to assist folks upgrading, we maintain a document describing information creation and request processing. • The proxy module (p. 504) has been revamped to bring it up to HTTP/1.1. Among the important changes, proxy access control is now placed inside a block rather than

More information is available at http://httpd.apache.org/docs-project/ Contents 1 Release Notes 1 1.1 Upgrading to 2.4 from 2.2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1094 Chapter 1 Release Notes 1 2 CHAPTER 1. RELEASE NOTES 1.1 Upgrading to 2.4 from 2.2 In order to assist folks upgrading, we maintain a document describing information which the autho- rization directives are applied. 1http://httpd.apache.org/docs/2.2/upgrading.html 1.1. UPGRADING TO 2.4 FROM 2.2 3 Directives that control how authorization modules respond when they don’t

More information is available at http://httpd.apache.org/docs-project/ Contents 1 Release Notes 1 1.1 Upgrading to 2.4 from 2.2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1080 x CONTENTS Chapter 1 Release Notes 1 2 CHAPTER 1. RELEASE NOTES 1.1 Upgrading to 2.4 from 2.2 In order to assist folks upgrading, we maintain a document describing information which the autho- rization directives are applied. 1http://httpd.apache.org/docs/2.2/upgrading.html 1.1. UPGRADING TO 2.4 FROM 2.2 3 Directives that control how authorization modules respond when they don’t

Caching Guide The Caching Guide has been rewritten to properly distinguish between the RFC2616 HTTP/1.1 caching features provided by mod_cache, and the generic key/value caching provided by the socache interface rewritten to take advantage of the new filter infrastructure and to implement a more reliable, HTTP/1.1 compliant proxy. In addition, new Copyright 2018 The Apache Software Foundation. Licensed seen something similar to: foo.example.com - - [12/Jul/2002:01:59:13 +0200] "GET /.htpasswd HTTP/1.1" in your Access Log. This means you probably commented out the following in your server configuration

Caching Guide The Caching Guide has been rewritten to properly distinguish between the RFC2616 HTTP/1.1 caching features provided by mod_cache, and the generic key/value caching provided by the socache interface rewritten to take advantage of the new filter infrastructure and to implement a more reliable, HTTP/1.1 compliant proxy. In addition, new Copyright 2017 The Apache Software Foundation. Licensed seen something similar to: foo.example.com - - [12/Jul/2002:01:59:13 +0200] "GET /.htpasswd HTTP/1.1" in your Access Log. This means you probably commented out the following in your server configuration

Caching Guide The Caching Guide has been rewritten to properly distinguish between the RFC2616 HTTP/1.1 caching features provided by mod_cache, and the generic key/value caching provided by the socache interface rewritten to take advantage of the new filter infrastructure and to implement a more reliable, HTTP/1.1 compliant proxy. In addition, new Copyright 2016 The Apache Software Foundation. Licensed seen something similar to: foo.example.com - - [12/Jul/2002:01:59:13 +0200] "GET /.htpasswd HTTP/1.1" in your Access Log. This means you probably commented out the following in your server configuration

Caching Guide The Caching Guide has been rewritten to properly distinguish between the RFC2616 HTTP/1.1 caching features provided by mod_cache, and the generic key/value caching provided by the socache interface rewritten to take advantage of the new filter infrastructure and to implement a more reliable, HTTP/1.1 compliant proxy. In addition, new Copyright 2016 The Apache Software Foundation. Licensed seen something similar to: foo.example.com - - [12/Jul/2002:01:59:13 +0200] "GET /.htpasswd HTTP/1.1" in your Access Log. This means you probably commented out the following in your server configuration

● Protocols – AJP – HTTP/HTTPS (1.1) – HTTP/2 (H2 and H2C) – Others proxy and Other protocols (web-socket etc) ● Configuration – mod_jk, mod_proxy, http/1.1 basic, h2c, h2 – https /TLS proxying encryption – Limited “authentication” (secret) ● mod_proxy_ajp and mod_jk 10/12/22 6 HTTP and HTTPS 1.1 ● When: – No SSL forwarding – Using SSLValve ● HTTP/HTTPS: – HTTPS might be needed (Encryption/Authentication) Nginx or GCE) ● Traffic Server ● Nginx 10/12/22 13 Other protocols ● Jboss-remoting ● Mix HTTP/1.1 websockets ● mod_proxy_wstunnel ● ProxySet "ws://localhost:8080/" upgrade=jboss-remoting ● LoadModule

rewritten to take advantage of the new filter infrastructure and to implement a more reliable, HTTP/1.1 compliant proxy. In addition, new configuration sections provide more readable (and internally used without any problems in almost all circumstances. However, if apr or apr-util, versions 1.0 or 1.1, are installed on your system, you must either upgrade your apr/apr-util installations to 1.2, force seen something similar to: foo.example.com - - [12/Jul/2002:01:59:13 +0200] "GET /.htpasswd HTTP/1.1" in your Access Log. This means you probably commented out the following in your server configuration

rewritten to take advantage of the new filter infrastructure and to implement a more reliable, HTTP/1.1 compliant proxy. In addition, new configuration sections provide more readable (and internally used without any problems in almost all circumstances. However, if apr or apr-util, versions 1.0 or 1.1, are installed on your system, you must either upgrade your apr/apr-util installations to 1.2, force seen something similar to: foo.example.com - - [12/Jul/2002:01:59:13 +0200] "GET /.htpasswd HTTP/1.1" in your Access Log. This means you probably commented out the following in your server configuration