Author: schultz
Date: Wed Nov 17 20:06:04 2021
New Revision: 1895119
URL: http://svn.apache.org/viewvc?rev=1895119&view=rev
Log:
Fix https://bz.apache.org/bugzilla/show_bug.cgi?id=65513
Update "notable changes" to include information about changes to the "Expires"
header handling.
Modified:
tomcat/site/trunk/docs/migration-10.1.html
tomcat/site/trunk/docs/migration-10.html
tomcat/site/trunk/docs/migration-85.html
tomcat/site/trunk/docs/migration-9.html
tomcat/site/trunk/xdocs/migration-10.1.xml
tomcat/site/trunk/xdocs/migration-10.xml
tomcat/site/trunk/xdocs/migration-85.xml
tomcat/site/trunk/xdocs/migration-9.xml
Modified: tomcat/site/trunk/docs/migration-10.1.html
URL:
http://svn.apache.org/viewvc/tomcat/site/trunk/docs/migration-10.1.html?rev=1895119&r1=1895118&r2=1895119&view=diff
==============================================================================
--- tomcat/site/trunk/docs/migration-10.1.html (original)
+++ tomcat/site/trunk/docs/migration-10.1.html Wed Nov 17 20:06:04 2021
@@ -100,7 +100,15 @@ of Apache Tomcat.</p>
are not fully backwards compatible and might cause breakage when
upgrading.</p>
<ul>
- <li>None</li>
+ <li><p>In 10.1.0-M3 onwards, Tomcat no longer adds an "Expires" HTTP
+ response header when adding "Cache-Control: private" due to a
+ CONFIDENTIAL transport-guarantee. This will likely cause a change
+ in caching behavior for applications that do not explicitly set
+ their own headers but rely on Tomcat's previous behavior. If you
+ with to disable caching, you will need to configure it explicitly
+ in your application. See
https://bz.apache.org/bugzilla/show_bug.cgi?id=65513
+ for more information.</p>
+ </li>
</ul>
</div></div>
Modified: tomcat/site/trunk/docs/migration-10.html
URL:
http://svn.apache.org/viewvc/tomcat/site/trunk/docs/migration-10.html?rev=1895119&r1=1895118&r2=1895119&view=diff
==============================================================================
--- tomcat/site/trunk/docs/migration-10.html (original)
+++ tomcat/site/trunk/docs/migration-10.html Wed Nov 17 20:06:04 2021
@@ -161,6 +161,15 @@ of Apache Tomcat.</p>
checks are complete. If the application is marked as serviced when the
method is called, the method will be a NO-OP.</p>
</li>
+ <li><p>In 10.0.9 onwards, Tomcat no longer adds an "Expires" HTTP
+ response header when adding "Cache-Control: private" due to a
+ CONFIDENTIAL transport-guarantee. This will likely cause a change
+ in caching behavior for applications that do not explicitly set
+ their own headers but rely on Tomcat's previous behavior. If you
+ with to disable caching, you will need to configure it explicitly
+ in your application. See
https://bz.apache.org/bugzilla/show_bug.cgi?id=65513
+ for more information.</p>
+ </li>
<li><p>In 10.0.11 onwards, as a result of the updated fork of Commons
FileUpload now using <code>java.nio.file.Files</code>, applications
using multi-part uploads need to ensure that the JVM is configured with
Modified: tomcat/site/trunk/docs/migration-85.html
URL:
http://svn.apache.org/viewvc/tomcat/site/trunk/docs/migration-85.html?rev=1895119&r1=1895118&r2=1895119&view=diff
==============================================================================
--- tomcat/site/trunk/docs/migration-85.html (original)
+++ tomcat/site/trunk/docs/migration-85.html Wed Nov 17 20:06:04 2021
@@ -254,6 +254,15 @@ of Apache Tomcat.</p>
checks are complete. If the application is marked as serviced when the
method is called, the method will be a NO-OP.</p>
</li>
+ <li><p>In 8.5.70 onwards, Tomcat no longer adds an "Expires" HTTP
+ response header when adding "Cache-Control: private" due to a
+ CONFIDENTIAL transport-guarantee. This will likely cause a change
+ in caching behavior for applications that do not explicitly set
+ their own headers but rely on Tomcat's previous behavior. If you
+ with to disable caching, you will need to configure it explicitly
+ in your application. See
https://bz.apache.org/bugzilla/show_bug.cgi?id=65513
+ for more information.</p>
+ </li>
<li><p>In 8.5.71 onwards, as a result of the updated fork of Commons
FileUpload now using <code>java.nio.file.Files</code>, applications
using multi-part uploads need to ensure that the JVM is configured with
Modified: tomcat/site/trunk/docs/migration-9.html
URL:
http://svn.apache.org/viewvc/tomcat/site/trunk/docs/migration-9.html?rev=1895119&r1=1895118&r2=1895119&view=diff
==============================================================================
--- tomcat/site/trunk/docs/migration-9.html (original)
+++ tomcat/site/trunk/docs/migration-9.html Wed Nov 17 20:06:04 2021
@@ -334,6 +334,15 @@ of Apache Tomcat.</p>
cause a startup error if they are present in the configuration, but
may produce a warning and will have no effect.</p>
</li>
+ <li><p>In 9.0.51 onwards, Tomcat no longer adds an "Expires" HTTP
+ response header when adding "Cache-Control: private" due to a
+ CONFIDENTIAL transport-guarantee. This will likely cause a change
+ in caching behavior for applications that do not explicitly set
+ their own headers but rely on Tomcat's previous behavior. If you
+ with to disable caching, you will need to configure it explicitly
+ in your application. See
https://bz.apache.org/bugzilla/show_bug.cgi?id=65513
+ for more information.</p>
+ </li>
<li><p>In 9.0.53 onwards, as a result of the updated fork of Commons
FileUpload now using <code>java.nio.file.Files</code>, applications
using multi-part uploads need to ensure that the JVM is configured with
@@ -427,25 +436,25 @@ of Apache Tomcat.</p>
<option value="9.0.50">9.0.50</option>
<option value="9.0.52">9.0.52</option>
<option value="9.0.53">9.0.53</option>
- <option value="9.0.54" selected>9.0.54</option>
- </select>,</label> <label>new version:
- <select name="hb">
- <option value="9.0.0-M1">9.0.0-M1</option>
- <option value="9.0.0-M3">9.0.0-M3</option>
- <option value="9.0.0-M4">9.0.0-M4</option>
- <option value="9.0.0-M6">9.0.0-M6</option>
- <option value="9.0.0-M8">9.0.0-M8</option>
- <option value="9.0.0-M9">9.0.0-M9</option>
- <option value="9.0.0-M10">9.0.0-M10</option>
- <option value="9.0.0-M11">9.0.0-M11</option>
- <option value="9.0.0-M13">9.0.0-M13</option>
- <option value="9.0.0-M15">9.0.0-M15</option>
- <option value="9.0.0-M17">9.0.0-M17</option>
- <option value="9.0.0-M18">9.0.0-M18</option>
- <option value="9.0.0-M19">9.0.0-M19</option>
- <option value="9.0.0-M20">9.0.0-M20</option>
- <option value="9.0.0-M21">9.0.0-M21</option>
- <option value="9.0.0-M22">9.0.0-M22</option>
+ <option value="9.0.54" selected>9.0.54</option>
+ </select>,</label> <label>new version:
+ <select name="hb">
+ <option value="9.0.0-M1">9.0.0-M1</option>
+ <option value="9.0.0-M3">9.0.0-M3</option>
+ <option value="9.0.0-M4">9.0.0-M4</option>
+ <option value="9.0.0-M6">9.0.0-M6</option>
+ <option value="9.0.0-M8">9.0.0-M8</option>
+ <option value="9.0.0-M9">9.0.0-M9</option>
+ <option value="9.0.0-M10">9.0.0-M10</option>
+ <option value="9.0.0-M11">9.0.0-M11</option>
+ <option value="9.0.0-M13">9.0.0-M13</option>
+ <option value="9.0.0-M15">9.0.0-M15</option>
+ <option value="9.0.0-M17">9.0.0-M17</option>
+ <option value="9.0.0-M18">9.0.0-M18</option>
+ <option value="9.0.0-M19">9.0.0-M19</option>
+ <option value="9.0.0-M20">9.0.0-M20</option>
+ <option value="9.0.0-M21">9.0.0-M21</option>
+ <option value="9.0.0-M22">9.0.0-M22</option>
<option value="9.0.0-M26">9.0.0-M26</option>
<option value="9.0.1">9.0.1</option>
<option value="9.0.2">9.0.2</option>
Modified: tomcat/site/trunk/xdocs/migration-10.1.xml
URL:
http://svn.apache.org/viewvc/tomcat/site/trunk/xdocs/migration-10.1.xml?rev=1895119&r1=1895118&r2=1895119&view=diff
==============================================================================
--- tomcat/site/trunk/xdocs/migration-10.1.xml (original)
+++ tomcat/site/trunk/xdocs/migration-10.1.xml Wed Nov 17 20:06:04 2021
@@ -113,7 +113,15 @@ of Apache Tomcat.</p>
are not fully backwards compatible and might cause breakage when
upgrading.</p>
<ul>
- <li>None</li>
+ <li><p>In 10.1.0-M3 onwards, Tomcat no longer adds an "Expires" HTTP
+ response header when adding "Cache-Control: private" due to a
+ CONFIDENTIAL transport-guarantee. This will likely cause a change
+ in caching behavior for applications that do not explicitly set
+ their own headers but rely on Tomcat's previous behavior. If you
+ with to disable caching, you will need to configure it explicitly
+ in your application. See
https://bz.apache.org/bugzilla/show_bug.cgi?id=65513
+ for more information.</p>
+ </li>
</ul>
</subsection>
Modified: tomcat/site/trunk/xdocs/migration-10.xml
URL:
http://svn.apache.org/viewvc/tomcat/site/trunk/xdocs/migration-10.xml?rev=1895119&r1=1895118&r2=1895119&view=diff
==============================================================================
--- tomcat/site/trunk/xdocs/migration-10.xml (original)
+++ tomcat/site/trunk/xdocs/migration-10.xml Wed Nov 17 20:06:04 2021
@@ -174,6 +174,15 @@ of Apache Tomcat.</p>
checks are complete. If the application is marked as serviced when the
method is called, the method will be a NO-OP.</p>
</li>
+ <li><p>In 10.0.9 onwards, Tomcat no longer adds an "Expires" HTTP
+ response header when adding "Cache-Control: private" due to a
+ CONFIDENTIAL transport-guarantee. This will likely cause a change
+ in caching behavior for applications that do not explicitly set
+ their own headers but rely on Tomcat's previous behavior. If you
+ with to disable caching, you will need to configure it explicitly
+ in your application. See
https://bz.apache.org/bugzilla/show_bug.cgi?id=65513
+ for more information.</p>
+ </li>
<li><p>In 10.0.11 onwards, as a result of the updated fork of Commons
FileUpload now using <code>java.nio.file.Files</code>, applications
using multi-part uploads need to ensure that the JVM is configured with
Modified: tomcat/site/trunk/xdocs/migration-85.xml
URL:
http://svn.apache.org/viewvc/tomcat/site/trunk/xdocs/migration-85.xml?rev=1895119&r1=1895118&r2=1895119&view=diff
==============================================================================
--- tomcat/site/trunk/xdocs/migration-85.xml (original)
+++ tomcat/site/trunk/xdocs/migration-85.xml Wed Nov 17 20:06:04 2021
@@ -267,6 +267,15 @@ of Apache Tomcat.</p>
checks are complete. If the application is marked as serviced when the
method is called, the method will be a NO-OP.</p>
</li>
+ <li><p>In 8.5.70 onwards, Tomcat no longer adds an "Expires" HTTP
+ response header when adding "Cache-Control: private" due to a
+ CONFIDENTIAL transport-guarantee. This will likely cause a change
+ in caching behavior for applications that do not explicitly set
+ their own headers but rely on Tomcat's previous behavior. If you
+ with to disable caching, you will need to configure it explicitly
+ in your application. See
https://bz.apache.org/bugzilla/show_bug.cgi?id=65513
+ for more information.</p>
+ </li>
<li><p>In 8.5.71 onwards, as a result of the updated fork of Commons
FileUpload now using <code>java.nio.file.Files</code>, applications
using multi-part uploads need to ensure that the JVM is configured with
Modified: tomcat/site/trunk/xdocs/migration-9.xml
URL:
http://svn.apache.org/viewvc/tomcat/site/trunk/xdocs/migration-9.xml?rev=1895119&r1=1895118&r2=1895119&view=diff
==============================================================================
--- tomcat/site/trunk/xdocs/migration-9.xml (original)
+++ tomcat/site/trunk/xdocs/migration-9.xml Wed Nov 17 20:06:04 2021
@@ -347,6 +347,15 @@ of Apache Tomcat.</p>
cause a startup error if they are present in the configuration, but
may produce a warning and will have no effect.</p>
</li>
+ <li><p>In 9.0.51 onwards, Tomcat no longer adds an "Expires" HTTP
+ response header when adding "Cache-Control: private" due to a
+ CONFIDENTIAL transport-guarantee. This will likely cause a change
+ in caching behavior for applications that do not explicitly set
+ their own headers but rely on Tomcat's previous behavior. If you
+ with to disable caching, you will need to configure it explicitly
+ in your application. See
https://bz.apache.org/bugzilla/show_bug.cgi?id=65513
+ for more information.</p>
+ </li>
<li><p>In 9.0.53 onwards, as a result of the updated fork of Commons
FileUpload now using <code>java.nio.file.Files</code>, applications
using multi-part uploads need to ensure that the JVM is configured with
@@ -442,25 +451,25 @@ of Apache Tomcat.</p>
<option value="9.0.50">9.0.50</option>
<option value="9.0.52">9.0.52</option>
<option value="9.0.53">9.0.53</option>
- <option value="9.0.54" selected="selected">9.0.54</option>
- </select>,</label> <label>new version:
- <select name="hb">
- <option value="9.0.0-M1">9.0.0-M1</option>
- <option value="9.0.0-M3">9.0.0-M3</option>
- <option value="9.0.0-M4">9.0.0-M4</option>
- <option value="9.0.0-M6">9.0.0-M6</option>
- <option value="9.0.0-M8">9.0.0-M8</option>
- <option value="9.0.0-M9">9.0.0-M9</option>
- <option value="9.0.0-M10">9.0.0-M10</option>
- <option value="9.0.0-M11">9.0.0-M11</option>
- <option value="9.0.0-M13">9.0.0-M13</option>
- <option value="9.0.0-M15">9.0.0-M15</option>
- <option value="9.0.0-M17">9.0.0-M17</option>
- <option value="9.0.0-M18">9.0.0-M18</option>
- <option value="9.0.0-M19">9.0.0-M19</option>
- <option value="9.0.0-M20">9.0.0-M20</option>
- <option value="9.0.0-M21">9.0.0-M21</option>
- <option value="9.0.0-M22">9.0.0-M22</option>
+ <option value="9.0.54" selected="selected">9.0.54</option>
+ </select>,</label> <label>new version:
+ <select name="hb">
+ <option value="9.0.0-M1">9.0.0-M1</option>
+ <option value="9.0.0-M3">9.0.0-M3</option>
+ <option value="9.0.0-M4">9.0.0-M4</option>
+ <option value="9.0.0-M6">9.0.0-M6</option>
+ <option value="9.0.0-M8">9.0.0-M8</option>
+ <option value="9.0.0-M9">9.0.0-M9</option>
+ <option value="9.0.0-M10">9.0.0-M10</option>
+ <option value="9.0.0-M11">9.0.0-M11</option>
+ <option value="9.0.0-M13">9.0.0-M13</option>
+ <option value="9.0.0-M15">9.0.0-M15</option>
+ <option value="9.0.0-M17">9.0.0-M17</option>
+ <option value="9.0.0-M18">9.0.0-M18</option>
+ <option value="9.0.0-M19">9.0.0-M19</option>
+ <option value="9.0.0-M20">9.0.0-M20</option>
+ <option value="9.0.0-M21">9.0.0-M21</option>
+ <option value="9.0.0-M22">9.0.0-M22</option>
<option value="9.0.0-M26">9.0.0-M26</option>
<option value="9.0.1">9.0.1</option>
<option value="9.0.2">9.0.2</option>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org
