svn commit: r1553650 - in /tomcat/trunk/webapps/docs/config: ajp.xml http.xml

2013-12-27 Thread markt
Author: markt
Date: Fri Dec 27 09:30:29 2013
New Revision: 1553650

URL: http://svn.apache.org/r1553650
Log:
Be more precise about how maxConnections works

Modified:
tomcat/trunk/webapps/docs/config/ajp.xml
tomcat/trunk/webapps/docs/config/http.xml

Modified: tomcat/trunk/webapps/docs/config/ajp.xml
URL: 
http://svn.apache.org/viewvc/tomcat/trunk/webapps/docs/config/ajp.xml?rev=1553650&r1=1553649&r2=1553650&view=diff
==
--- tomcat/trunk/webapps/docs/config/ajp.xml (original)
+++ tomcat/trunk/webapps/docs/config/ajp.xml Fri Dec 27 09:30:29 2013
@@ -357,10 +357,13 @@
 
   The maximum number of connections that the server will accept and
   process at any given time. When this number has been reached, the server
-  will not accept any more connections until the number of connections
-  falls below this value. The operating system may still accept
-  connections based on the acceptCount setting. Default value
-  varies by connector type. For BIO the default is the value of
+  will accept, but not process, one further connection. This additional
+  connection be blocked until the number of connections being processed
+  falls below maxConnections at which point the server 
will
+  start accepting and processing new connections again. Note that once the
+  limit has been reached, the operating system may still accept connections
+  based on the acceptCount setting. The default value varies 
by
+  connector type. For BIO the default is the value of
   maxThreads unless an Executor
   is used in which case the default will be the value of maxThreads from 
the
   executor. For NIO the default is 1.

Modified: tomcat/trunk/webapps/docs/config/http.xml
URL: 
http://svn.apache.org/viewvc/tomcat/trunk/webapps/docs/config/http.xml?rev=1553650&r1=1553649&r2=1553650&view=diff
==
--- tomcat/trunk/webapps/docs/config/http.xml (original)
+++ tomcat/trunk/webapps/docs/config/http.xml Fri Dec 27 09:30:29 2013
@@ -396,10 +396,13 @@
 
   The maximum number of connections that the server will accept and
   process at any given time. When this number has been reached, the server
-  will not accept any more connections until the number of connections
-  falls below this value. The operating system may still accept
-  connections based on the acceptCount setting. Default value
-  varies by connector type. For BIO the default is the value of
+  will accept, but not process, one further connection. This additional
+  connection be blocked until the number of connections being processed
+  falls below maxConnections at which point the server 
will
+  start accepting and processing new connections again. Note that once the
+  limit has been reached, the operating system may still accept connections
+  based on the acceptCount setting. The default value varies 
by
+  connector type. For BIO the default is the value of
   maxThreads unless an Executor
   is used in which case the default will be the value of maxThreads from 
the
   executor. For NIO the default is 1.



-
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org



svn commit: r1553651 - in /tomcat/tc7.0.x/trunk: ./ webapps/docs/changelog.xml webapps/docs/config/ajp.xml webapps/docs/config/http.xml

2013-12-27 Thread markt
Author: markt
Date: Fri Dec 27 09:35:41 2013
New Revision: 1553651

URL: http://svn.apache.org/r1553651
Log:
Be more precise about how maxConnections works

Modified:
tomcat/tc7.0.x/trunk/   (props changed)
tomcat/tc7.0.x/trunk/webapps/docs/changelog.xml
tomcat/tc7.0.x/trunk/webapps/docs/config/ajp.xml
tomcat/tc7.0.x/trunk/webapps/docs/config/http.xml

Propchange: tomcat/tc7.0.x/trunk/
--
  Merged /tomcat/trunk:r1553650

Modified: tomcat/tc7.0.x/trunk/webapps/docs/changelog.xml
URL: 
http://svn.apache.org/viewvc/tomcat/tc7.0.x/trunk/webapps/docs/changelog.xml?rev=1553651&r1=1553650&r2=1553651&view=diff
==
--- tomcat/tc7.0.x/trunk/webapps/docs/changelog.xml (original)
+++ tomcat/tc7.0.x/trunk/webapps/docs/changelog.xml Fri Dec 27 09:35:41 2013
@@ -80,7 +80,12 @@
   
   
 Clarify that the connectionTimeout may also be used as the read timeout
-when reading a request body (if any). (markt) 
+when reading a request body (if any) in the documentation web
+application. (markt) 
+  
+  
+Clarify the behaviour of the maxConnections attribute for a connector 
in
+the documentation web application. (markt) 
   
 
   

Modified: tomcat/tc7.0.x/trunk/webapps/docs/config/ajp.xml
URL: 
http://svn.apache.org/viewvc/tomcat/tc7.0.x/trunk/webapps/docs/config/ajp.xml?rev=1553651&r1=1553650&r2=1553651&view=diff
==
--- tomcat/tc7.0.x/trunk/webapps/docs/config/ajp.xml (original)
+++ tomcat/tc7.0.x/trunk/webapps/docs/config/ajp.xml Fri Dec 27 09:35:41 2013
@@ -355,10 +355,13 @@
 
   The maximum number of connections that the server will accept and
   process at any given time. When this number has been reached, the server
-  will not accept any more connections until the number of connections
-  falls below this value. The operating system may still accept
-  connections based on the acceptCount setting. Default value
-  varies by connector type. For BIO the default is the value of
+  will accept, but not process, one further connection. This additional
+  connection be blocked until the number of connections being processed
+  falls below maxConnections at which point the server 
will
+  start accepting and processing new connections again. Note that once the
+  limit has been reached, the operating system may still accept connections
+  based on the acceptCount setting. The default value varies 
by
+  connector type. For BIO the default is the value of
   maxThreads unless an Executor
   is used in which case the default will be the value of maxThreads from 
the
   executor. For NIO the default is 1.

Modified: tomcat/tc7.0.x/trunk/webapps/docs/config/http.xml
URL: 
http://svn.apache.org/viewvc/tomcat/tc7.0.x/trunk/webapps/docs/config/http.xml?rev=1553651&r1=1553650&r2=1553651&view=diff
==
--- tomcat/tc7.0.x/trunk/webapps/docs/config/http.xml (original)
+++ tomcat/tc7.0.x/trunk/webapps/docs/config/http.xml Fri Dec 27 09:35:41 2013
@@ -393,10 +393,13 @@
 
   The maximum number of connections that the server will accept and
   process at any given time. When this number has been reached, the server
-  will not accept any more connections until the number of connections
-  falls below this value. The operating system may still accept
-  connections based on the acceptCount setting. Default value
-  varies by connector type. For BIO the default is the value of
+  will accept, but not process, one further connection. This additional
+  connection be blocked until the number of connections being processed
+  falls below maxConnections at which point the server 
will
+  start accepting and processing new connections again. Note that once the
+  limit has been reached, the operating system may still accept connections
+  based on the acceptCount setting. The default value varies 
by
+  connector type. For BIO the default is the value of
   maxThreads unless an Executor
   is used in which case the default will be the value of maxThreads from 
the
   executor. For NIO the default is 1.



-
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org



JDK 8 Build 121 & JDK 7 Update 60 build 02 are available on java.net

2013-12-27 Thread Rory O'Donnell Oracle, Dublin Ireland

Hi Mladen

Hope you are enjoying the holidays, all the best for 2014.

JDK 8 Build b121 Early Access Build is now available for download 
 & test.
JDK 7u60 b02 Early Access Build is also available for download 
& test.


We are now very late in the release cycle of JDK 8 , issues found late may
be postponed to JDK 9 time frame. Please log all show stopper issues as
soon as possible.

Thanks for your support, Rory

--
Rgds,Rory O'Donnell
Quality Engineering Manager
Oracle EMEA , Dublin, Ireland



svn commit: r1553679 - in /tomcat/trunk: java/org/apache/catalina/ java/org/apache/catalina/core/ java/org/apache/catalina/webresources/ test/org/apache/catalina/webresources/

2013-12-27 Thread markt
Author: markt
Date: Fri Dec 27 14:38:46 2013
New Revision: 1553679

URL: http://svn.apache.org/r1553679
Log:
Align names between 7.0.x and 8.0.x

Modified:
tomcat/trunk/java/org/apache/catalina/WebResourceRoot.java
tomcat/trunk/java/org/apache/catalina/core/StandardContext.java
tomcat/trunk/java/org/apache/catalina/webresources/Cache.java
tomcat/trunk/java/org/apache/catalina/webresources/CachedResource.java
tomcat/trunk/java/org/apache/catalina/webresources/LocalStrings.properties
tomcat/trunk/java/org/apache/catalina/webresources/StandardRoot.java

tomcat/trunk/test/org/apache/catalina/webresources/TesterWebResourceRoot.java

Modified: tomcat/trunk/java/org/apache/catalina/WebResourceRoot.java
URL: 
http://svn.apache.org/viewvc/tomcat/trunk/java/org/apache/catalina/WebResourceRoot.java?rev=1553679&r1=1553678&r2=1553679&view=diff
==
--- tomcat/trunk/java/org/apache/catalina/WebResourceRoot.java (original)
+++ tomcat/trunk/java/org/apache/catalina/WebResourceRoot.java Fri Dec 27 
14:38:46 2013
@@ -349,10 +349,10 @@ public interface WebResourceRoot extends
  * Set the maximum permitted size for a single object in the cache. Note
  * that the maximum size in bytes may not exceed {@link Integer#MAX_VALUE}.
  *
- * @param cacheMaxObjectSizeMaximum size for a single cached object in
+ * @param cacheObjectMaxSizeMaximum size for a single cached object in
  *  kilobytes
  */
-void setCacheMaxObjectSize(int cacheMaxObjectSize);
+void setCacheObjectMaxSize(int cacheObjectMaxSize);
 
 /**
  * Get the maximum permitted size for a single object in the cache. Note
@@ -360,7 +360,7 @@ public interface WebResourceRoot extends
  *
  * @return  Maximum size for a single cached object in kilobytes
  */
-int getCacheMaxObjectSize();
+int getCacheObjectMaxSize();
 
 /**
  * Controls whether the trace locked files feature is enabled. If enabled,

Modified: tomcat/trunk/java/org/apache/catalina/core/StandardContext.java
URL: 
http://svn.apache.org/viewvc/tomcat/trunk/java/org/apache/catalina/core/StandardContext.java?rev=1553679&r1=1553678&r2=1553679&view=diff
==
--- tomcat/trunk/java/org/apache/catalina/core/StandardContext.java (original)
+++ tomcat/trunk/java/org/apache/catalina/core/StandardContext.java Fri Dec 27 
14:38:46 2013
@@ -4912,7 +4912,7 @@ public class StandardContext extends Con
 resources.setCachingAllowed(isCachingAllowed());
 resources.setCacheTtl(getCacheTTL());
 resources.setCacheMaxSize(getCacheMaxSize());
-resources.setCacheMaxObjectSize(getCacheObjectMaxSize());
+resources.setCacheObjectMaxSize(getCacheObjectMaxSize());
 
 // May have been started (but not fully configured) in init() so no 
need
 // to start the resources if they are already available

Modified: tomcat/trunk/java/org/apache/catalina/webresources/Cache.java
URL: 
http://svn.apache.org/viewvc/tomcat/trunk/java/org/apache/catalina/webresources/Cache.java?rev=1553679&r1=1553678&r2=1553679&view=diff
==
--- tomcat/trunk/java/org/apache/catalina/webresources/Cache.java (original)
+++ tomcat/trunk/java/org/apache/catalina/webresources/Cache.java Fri Dec 27 
14:38:46 2013
@@ -42,7 +42,7 @@ public class Cache {
 
 private long ttl = 5000;
 private long maxSize = 10 * 1024 * 1024;
-private int maxObjectSize =
+private int objectMaxSize =
 (int) (maxSize / 20 > Integer.MAX_VALUE ? Integer.MAX_VALUE : 
maxSize / 20);
 
 private AtomicLong lookupCount = new AtomicLong(0);
@@ -72,9 +72,9 @@ public class Cache {
 
 if (cacheEntry == null) {
 // Local copy to ensure consistency
-int maxObjectSizeBytes = getMaxObjectSizeBytes();
+int objectMaxSizeBytes = getObjectMaxSizeBytes();
 CachedResource newCacheEntry =
-new CachedResource(root, path, getTtl(), 
maxObjectSizeBytes);
+new CachedResource(root, path, getTtl(), 
objectMaxSizeBytes);
 
 // Concurrent callers will end up with the same CachedResource
 // instance
@@ -211,23 +211,22 @@ public class Cache {
 return hitCount.get();
 }
 
-public void setMaxObjectSize(int maxObjectSize) {
-if (maxObjectSize * 1024L > Integer.MAX_VALUE) {
-log.warn(sm.getString("cache.maxObjectSizeTooBig",
-Integer.valueOf(maxObjectSize)));
-this.maxObjectSize = Integer.MAX_VALUE;
+public void setObjectMaxSize(int objectMaxSize) {
+if (objectMaxSize * 1024L > Integer.MAX_VALUE) {
+log.warn(sm.getString("cache.objectMaxSizeTooBig", 
Integer.valueOf(objectMaxSize)));
+  

Re: [VOTE] Release Apache Tomcat 7.0.50

2013-12-27 Thread Mark Thomas
On 20/12/2013 12:52, Violeta Georgieva wrote:
> The proposed Apache Tomcat 7.0.50 release is now available for voting.
> 
> It can be obtained from:
> https://dist.apache.org/repos/dist/dev/tomcat/tomcat-7/v7.0.50/
> The Maven staging repo is:
> https://repository.apache.org/content/repositories/orgapachetomcat-004/
> The svn tag is:
> http://svn.apache.org/repos/asf/tomcat/tc7.0.x/tags/TOMCAT_7_0_50/
> 
> The proposed 7.0.50 release is:
> [ ] Broken - do not release
> [X] Stable - go ahead and release as 7.0.50 Stable

My tests all pass.

Mark


-
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org



[Bug 55937] New: Tomcat auto deployer not working for ROOT applications

2013-12-27 Thread bugzilla
https://issues.apache.org/bugzilla/show_bug.cgi?id=55937

Bug ID: 55937
   Summary: Tomcat auto deployer not working for ROOT applications
   Product: Tomcat 7
   Version: 7.0.47
  Hardware: All
OS: Linux
Status: NEW
  Severity: minor
  Priority: P2
 Component: Manager
  Assignee: dev@tomcat.apache.org
  Reporter: jsb_apa...@360works.com

Created attachment 31162
  --> https://issues.apache.org/bugzilla/attachment.cgi?id=31162&action=edit
catalina and localhost logs

I am trying to deploy a web app as the ROOT application for Tomcat 7, running
on Ubuntu 12 with Amazon EC2. I experienced the problem with 7.0.35, 7.0.42,
and 7.0.49.

1) When I use auto-deploy using the Tomcat Deployer 'deploy' ant task to a
non-ROOT context name, such as /360Site, everything works as expected - war
file is uploaded, decompressed to directory, and is immediately available.

2) When I use the manager HTML interface to upload the ROOT.war file by
clicking the 'Select WAR file to upload' and then clicking 'deploy', everything
works as expected.

However, 3) When I do exactly the same thing as #1 (tomcat auto deploy) but
just change the 'path' variable from /360Store to /ROOT, here is what happens:
* WAR file appears in the webapps directory, but does not get expanded.
* The webapp is not running (I get a blank page when I go to the URL in the
browser)
* I see these entries in the catalina..log (after doing the auto-deploy:


Dec 27, 2013 3:34:03 PM org.apache.catalina.startup.HostConfig
deleteRedeployResources
INFO: Undeploying context []
Dec 27, 2013 3:34:03 PM org.apache.catalina.loader.WebappClassLoader
clearReferencesJdbc
SEVERE: The web application [] registered the JDBC driver
[com.mysql.jdbc.Driver] but failed to unregister it when the web application
was stopped. To prevent a memory leak, the JDBC Driver has been forcibly
unregistered.
Dec 27, 2013 3:34:03 PM org.apache.catalina.startup.HostConfig deployWAR
INFO: Deploying web application archive /var/lib/tomcat7/webapps/ROOT.war
Dec 27, 2013 3:34:04 PM org.apache.catalina.startup.ContextConfig init
SEVERE: Exception fixing docBase for context []
java.util.zip.ZipException: error in opening zip file
at java.util.zip.ZipFile.open(Native Method)
at java.util.zip.ZipFile.(ZipFile.java:215)
at java.util.zip.ZipFile.(ZipFile.java:145)
at java.util.jar.JarFile.(JarFile.java:153)
at java.util.jar.JarFile.(JarFile.java:90)
at sun.net.www.protocol.jar.URLJarFile.(URLJarFile.java:93)
at sun.net.www.protocol.jar.URLJarFile.getJarFile(URLJarFile.java:69)
at sun.net.www.protocol.jar.JarFileFactory.get(JarFileFactory.java:88)
at
sun.net.www.protocol.jar.JarURLConnection.connect(JarURLConnection.java:122)
at
sun.net.www.protocol.jar.JarURLConnection.getJarFile(JarURLConnection.java:89)
at org.apache.catalina.startup.ExpandWar.expand(ExpandWar.java:113)
at
org.apache.catalina.startup.ContextConfig.fixDocBase(ContextConfig.java:722)
at org.apache.catalina.startup.ContextConfig.init(ContextConfig.java:843)
at
org.apache.catalina.startup.ContextConfig.lifecycleEvent(ContextConfig.java:387)
at
org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:119)
at
org.apache.catalina.util.LifecycleBase.fireLifecycleEvent(LifecycleBase.java:90)
at
org.apache.catalina.util.LifecycleBase.setStateInternal(LifecycleBase.java:402)
at org.apache.catalina.util.LifecycleBase.init(LifecycleBase.java:110)
at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:139)
at
org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:901)
at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:877)
at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:633)
at org.apache.catalina.startup.HostConfig.deployWAR(HostConfig.java:983)
at
org.apache.catalina.startup.HostConfig$DeployWar.run(HostConfig.java:1660)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
at java.util.concurrent.FutureTask.run(FutureTask.java:166)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:724)

Dec 27, 2013 3:34:04 PM org.apache.catalina.core.StandardContext resourcesStart
SEVERE: Error starting static Resources
java.lang.IllegalArgumentException: Invalid or unreadable WAR file : error in
opening zip file
at
org.apache.naming.resources.WARDirContext.setDocBase(WARDirContext.java:138)
at
org.apache.catalina.core.StandardContext.resourcesStart(StandardContext.java:5055)
at
org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5235)
at org.apache.catalina.util

svn commit: r1553689 - in /tomcat/site/trunk: build.properties.default xdocs/doap_Tomcat.rdf xdocs/download-80.xml xdocs/index.xml xdocs/migration-8.xml xdocs/oldnews.xml xdocs/whichversion.xml

2013-12-27 Thread markt
Author: markt
Date: Fri Dec 27 16:24:45 2013
New Revision: 1553689

URL: http://svn.apache.org/r1553689
Log:
Updates for 8.0.0-RC10 release (less docs update)

Modified:
tomcat/site/trunk/build.properties.default
tomcat/site/trunk/xdocs/doap_Tomcat.rdf
tomcat/site/trunk/xdocs/download-80.xml
tomcat/site/trunk/xdocs/index.xml
tomcat/site/trunk/xdocs/migration-8.xml
tomcat/site/trunk/xdocs/oldnews.xml
tomcat/site/trunk/xdocs/whichversion.xml

Modified: tomcat/site/trunk/build.properties.default
URL: 
http://svn.apache.org/viewvc/tomcat/site/trunk/build.properties.default?rev=1553689&r1=1553688&r2=1553689&view=diff
==
--- tomcat/site/trunk/build.properties.default (original)
+++ tomcat/site/trunk/build.properties.default Fri Dec 27 16:24:45 2013
@@ -38,7 +38,7 @@ tomcat.loc=http://www.apache.org/dist/to
 # - Tomcat versions -
 tomcat60=6.0.36
 tomcat70=7.0.47
-tomcat80=8.0.0-RC5
+tomcat80=8.0.0-RC10
 
 
 # - Download destination -

Modified: tomcat/site/trunk/xdocs/doap_Tomcat.rdf
URL: 
http://svn.apache.org/viewvc/tomcat/site/trunk/xdocs/doap_Tomcat.rdf?rev=1553689&r1=1553688&r2=1553689&view=diff
==
--- tomcat/site/trunk/xdocs/doap_Tomcat.rdf (original)
+++ tomcat/site/trunk/xdocs/doap_Tomcat.rdf Fri Dec 27 16:24:45 2013
@@ -57,8 +57,8 @@
 
   
 Latest 8.0.x Release (Non-stable)
-2013-10-20
-8.0.0-RC5 (alpha)
+2013-12-26
+8.0.0-RC10 (alpha)
   
 
 

Modified: tomcat/site/trunk/xdocs/download-80.xml
URL: 
http://svn.apache.org/viewvc/tomcat/site/trunk/xdocs/download-80.xml?rev=1553689&r1=1553688&r2=1553689&view=diff
==
--- tomcat/site/trunk/xdocs/download-80.xml (original)
+++ tomcat/site/trunk/xdocs/download-80.xml Fri Dec 27 16:24:45 2013
@@ -15,8 +15,8 @@
   
   
 https://www.apache.org/dist/tomcat/tomcat-8/KEYS";>KEYS |
-8.0.0-RC5 |
-Browse |
+8.0.0-RC10 |
+Browse |
 http://archive.apache.org/dist/tomcat/tomcat-8";>Archives
   
   
@@ -58,11 +58,11 @@
   
   
 
-  
-  
+  
+  
   
   Please see the 
-  README
+  README
   file for packaging information.  It explains what every distribution 
contains.
   
 
@@ -71,121 +71,121 @@
 Core:
   
   
-zip 
-(https://www.apache.org/dist/tomcat/tomcat-8/v8.0.0-RC5/bin/apache-tomcat-8.0.0-RC5.zip.asc";>pgp,
 
-https://www.apache.org/dist/tomcat/tomcat-8/v8.0.0-RC5/bin/apache-tomcat-8.0.0-RC5.zip.md5";>md5)
+zip 
+(https://www.apache.org/dist/tomcat/tomcat-8/v8.0.0-RC10/bin/apache-tomcat-8.0.0-RC10.zip.asc";>pgp,
 
+https://www.apache.org/dist/tomcat/tomcat-8/v8.0.0-RC10/bin/apache-tomcat-8.0.0-RC10.zip.md5";>md5)
   
   
-tar.gz 
-(https://www.apache.org/dist/tomcat/tomcat-8/v8.0.0-RC5/bin/apache-tomcat-8.0.0-RC5.tar.gz.asc";>pgp,
 
-https://www.apache.org/dist/tomcat/tomcat-8/v8.0.0-RC5/bin/apache-tomcat-8.0.0-RC5.tar.gz.md5";>md5)
+tar.gz 
+(https://www.apache.org/dist/tomcat/tomcat-8/v8.0.0-RC10/bin/apache-tomcat-8.0.0-RC10.tar.gz.asc";>pgp,
 
+https://www.apache.org/dist/tomcat/tomcat-8/v8.0.0-RC10/bin/apache-tomcat-8.0.0-RC10.tar.gz.md5";>md5)
   
   
-32-bit Windows zip 
-(https://www.apache.org/dist/tomcat/tomcat-8/v8.0.0-RC5/bin/apache-tomcat-8.0.0-RC5-windows-x86.zip.asc";>pgp,
 
-https://www.apache.org/dist/tomcat/tomcat-8/v8.0.0-RC5/bin/apache-tomcat-8.0.0-RC5-windows-x86.zip.md5";>md5)
+32-bit Windows zip 
+(https://www.apache.org/dist/tomcat/tomcat-8/v8.0.0-RC10/bin/apache-tomcat-8.0.0-RC10-windows-x86.zip.asc";>pgp,
 
+https://www.apache.org/dist/tomcat/tomcat-8/v8.0.0-RC10/bin/apache-tomcat-8.0.0-RC10-windows-x86.zip.md5";>md5)
   
   
-64-bit Windows zip 
-(https://www.apache.org/dist/tomcat/tomcat-8/v8.0.0-RC5/bin/apache-tomcat-8.0.0-RC5-windows-x64.zip.asc";>pgp,
 
-https://www.apache.org/dist/tomcat/tomcat-8/v8.0.0-RC5/bin/apache-tomcat-8.0.0-RC5-windows-x64.zip.md5";>md5)
+64-bit Windows zip 
+(https://www.apache.org/dist/tomcat/tomcat-8/v8.0.0-RC10/bin/apache-tomcat-8.0.0-RC10-windows-x64.zip.asc";>pgp,
 
+https://www.apache.org/dist/tomcat/tomcat-8/v8.0.0-RC10/bin/apache-tomcat-8.0.0-RC10-windows-x64.zip.md5";>md5)
   
   
-64-bit Itanium Windows zip 
-(https://www.apache.org/dist/tomcat/tomcat-8/v8.0.0-RC5/bin/apache-tomcat-8.0.0-RC5-windows-i64.zip.asc";>pgp,
 
-https://www.apache.org/dist/tomcat/tomcat-8/v8.0.

svn commit: r1553690 - in /tomcat/site/trunk/docs: doap_Tomcat.rdf download-80.html index.html migration-8.html oldnews.html whichversion.html

2013-12-27 Thread markt
Author: markt
Date: Fri Dec 27 16:25:30 2013
New Revision: 1553690

URL: http://svn.apache.org/r1553690
Log:
Updates for 8.0.0-RC10 release (generated pages, less docs update)

Modified:
tomcat/site/trunk/docs/doap_Tomcat.rdf
tomcat/site/trunk/docs/download-80.html
tomcat/site/trunk/docs/index.html
tomcat/site/trunk/docs/migration-8.html
tomcat/site/trunk/docs/oldnews.html
tomcat/site/trunk/docs/whichversion.html

Modified: tomcat/site/trunk/docs/doap_Tomcat.rdf
URL: 
http://svn.apache.org/viewvc/tomcat/site/trunk/docs/doap_Tomcat.rdf?rev=1553690&r1=1553689&r2=1553690&view=diff
==
--- tomcat/site/trunk/docs/doap_Tomcat.rdf (original)
+++ tomcat/site/trunk/docs/doap_Tomcat.rdf Fri Dec 27 16:25:30 2013
@@ -57,8 +57,8 @@
 
   
 Latest 8.0.x Release (Non-stable)
-2013-10-20
-8.0.0-RC5 (alpha)
+2013-12-26
+8.0.0-RC10 (alpha)
   
 
 

Modified: tomcat/site/trunk/docs/download-80.html
URL: 
http://svn.apache.org/viewvc/tomcat/site/trunk/docs/download-80.html?rev=1553690&r1=1553689&r2=1553690&view=diff
==
--- tomcat/site/trunk/docs/download-80.html (original)
+++ tomcat/site/trunk/docs/download-80.html Fri Dec 27 16:25:30 2013
@@ -204,8 +204,8 @@
 
 
 https://www.apache.org/dist/tomcat/tomcat-8/KEYS";>KEYS |
-8.0.0-RC5 |
-Browse |
+8.0.0-RC10 |
+Browse |
 http://archive.apache.org/dist/tomcat/tomcat-8";>Archives
   
 
@@ -251,12 +251,12 @@

   
 
-8.0.0-RC5
+8.0.0-RC10
 
   
 
   Please see the 
-  README
+  README
   file for packaging information.  It explains what every distribution 
contains.
   
 
@@ -272,44 +272,44 @@
   
 
 
-zip 
-(https://www.apache.org/dist/tomcat/tomcat-8/v8.0.0-RC5/bin/apache-tomcat-8.0.0-RC5.zip.asc";>pgp,
 
-https://www.apache.org/dist/tomcat/tomcat-8/v8.0.0-RC5/bin/apache-tomcat-8.0.0-RC5.zip.md5";>md5)
+zip 
+(https://www.apache.org/dist/tomcat/tomcat-8/v8.0.0-RC10/bin/apache-tomcat-8.0.0-RC10.zip.asc";>pgp,
 
+https://www.apache.org/dist/tomcat/tomcat-8/v8.0.0-RC10/bin/apache-tomcat-8.0.0-RC10.zip.md5";>md5)
   
   
 
 
-tar.gz 
-(https://www.apache.org/dist/tomcat/tomcat-8/v8.0.0-RC5/bin/apache-tomcat-8.0.0-RC5.tar.gz.asc";>pgp,
 
-https://www.apache.org/dist/tomcat/tomcat-8/v8.0.0-RC5/bin/apache-tomcat-8.0.0-RC5.tar.gz.md5";>md5)
+tar.gz 
+(https://www.apache.org/dist/tomcat/tomcat-8/v8.0.0-RC10/bin/apache-tomcat-8.0.0-RC10.tar.gz.asc";>pgp,
 
+https://www.apache.org/dist/tomcat/tomcat-8/v8.0.0-RC10/bin/apache-tomcat-8.0.0-RC10.tar.gz.md5";>md5)
   
   
 
 
-32-bit Windows zip 
-(https://www.apache.org/dist/tomcat/tomcat-8/v8.0.0-RC5/bin/apache-tomcat-8.0.0-RC5-windows-x86.zip.asc";>pgp,
 
-https://www.apache.org/dist/tomcat/tomcat-8/v8.0.0-RC5/bin/apache-tomcat-8.0.0-RC5-windows-x86.zip.md5";>md5)
+32-bit Windows zip 
+(https://www.apache.org/dist/tomcat/tomcat-8/v8.0.0-RC10/bin/apache-tomcat-8.0.0-RC10-windows-x86.zip.asc";>pgp,
 
+https://www.apache.org/dist/tomcat/tomcat-8/v8.0.0-RC10/bin/apache-tomcat-8.0.0-RC10-windows-x86.zip.md5";>md5)
   
   
 
 
-64-bit Windows zip 
-(https://www.apache.org/dist/tomcat/tomcat-8/v8.0.0-RC5/bin/apache-tomcat-8.0.0-RC5-windows-x64.zip.asc";>pgp,
 
-https://www.apache.org/dist/tomcat/tomcat-8/v8.0.0-RC5/bin/apache-tomcat-8.0.0-RC5-windows-x64.zip.md5";>md5)
+64-bit Windows zip 
+(https://www.apache.org/dist/tomcat/tomcat-8/v8.0.0-RC10/bin/apache-tomcat-8.0.0-RC10-windows-x64.zip.asc";>pgp,
 
+https://www.apache.org/dist/tomcat/tomcat-8/v8.0.0-RC10/bin/apache-tomcat-8.0.0-RC10-windows-x64.zip.md5";>md5)
   
   
 
 
-64-bit Itanium Windows zip 
-(https://www.apache.org/dist/tomcat/tomcat-8/v8.0.0-RC5/bin/apache-tomcat-8.0.0-RC5-windows-i64.zip.asc";>pgp,
 
-https://www.apache.org/dist/tomcat/tomcat-8/v8.0.0-RC5/bin/apache-tomcat-8.0.0-RC5-windows-i64.zip.md5";>md5)
+64-bit Itanium Windows zip 
+(https://www.apache.org/dist/tomcat/tomcat-8/v8.0.0-RC10/bin/apache-tomcat-8.0.0-RC10-windows-i64.zip.asc";>pgp,
 
+https://www.apache.org/dist/tomcat/tomcat-8/v8.0.0-RC10/bin/apache-tomcat-8.0.0-RC10-windows-i64.zip.md5";>md5)
   
   
 
 
-32-bit/64-bit Windows Service Installer 
-(https://www.apache.org/dist/tomcat/tomcat-8/v8.0.0-RC5/bin/apache-tomcat-8.0.0-RC5.exe.asc";>pgp,
 
-https://www.apache.org/dist/tomcat/tomcat-8/v8.0.0-RC5/bin/apache-tomcat-8.0.0-RC5.exe.md5";>md5)
+32-bit/64-bit Windows Service Installer 
+ 

svn commit: r3994 - /release/tomcat/tomcat-8/v8.0.0-RC5/

2013-12-27 Thread markt
Author: markt
Date: Fri Dec 27 16:33:42 2013
New Revision: 3994

Log:
Drop 8.0.0-RC5 from the mirrors

Removed:
release/tomcat/tomcat-8/v8.0.0-RC5/


-
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org



svn commit: r3994 - /release/tomcat/tomcat-8/v8.0.0-RC5/

2013-12-27 Thread markt
Author: markt
Date: Fri Dec 27 16:33:42 2013
New Revision: 3994

Log:
Drop 8.0.0-RC5 from the mirrors

Removed:
release/tomcat/tomcat-8/v8.0.0-RC5/


-
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org



[ANN] Apache Tomcat 8.0.0-RC10 (alpha) available

2013-12-27 Thread Mark Thomas
The Apache Tomcat team announces the immediate availability of Apache
Tomcat 8.0.0-RC10 (alpha).

Apache Tomcat 8 is an open source software implementation of the Java
Servlet, JavaServer Pages, Java Unified Expression Language and Java
WebSocket technologies.

Apache Tomcat 8 is aligned with Java EE 7. In addition to supporting
updated versions of the Java EE specifications, Tomcat 8 includes a
number of improvements compared to Tomcat 7. The notable changes
include:

- Support for Java Servlet 3.1, JavaServer Pages 2.3, Java Unified
  Expression Language 3.0 and Java WebSocket 1.0.

- The default connector implementation is now the Java non-blocking
  implementation (NIO) for both HTTP and AJP.

- A new resources implementation that replaces Aliases, VirtualLoader,
  VirtualDirContext, JAR resources and external repositories with a
  single, consistent approach for configuring additional web
  application resources. The new resources implementation can also be
  used to implement overlays (using a master WAR as the basis for
  multiple web applications that each have their own
  customizations).


Apache Tomcat 8.0.0-RC10 includes numerous fixes for issues identified
in RC5 as well as a number of other enhancements and changes. The
notable changes since RC5 include:

- Extending the new resources implementation to include resource
  handling for class loaders and the addition of a new feature to track
  the code responsible for an open file.

- Complete refactoring of TLD handling including the addition of
  caching of parsed TLDs to improve performance.

- Improvements to JMX MBeans including better visibility of DBCP
  connection pools and improved organisation in the default JConsole
  view.


Please refer to the change log for the complete list of changes:
http://tomcat.apache.org/tomcat-8.0-doc/changelog.html

The purpose of this release candidate is to give users an opportunity to
test Tomcat 8 and provide feedback to the Tomcat community. It has been
given an alpha status which means that it is not judged as being ready
for production usage. The implementations of the 4 Java EE 7
specifications are all complete but there is some internal refactoring
to be completed before the alpha label is removed.

Note: This version has 4 zip binaries: a generic one and three
  bundled with Tomcat native binaries for Windows operating systems
  running on different CPU architectures.

Downloads:
http://tomcat.apache.org/download-80.cgi

Migration guides from Apache Tomcat 5.5.x, 6.0.x and 7.0.x:
http://tomcat.apache.org/migration.html

Enjoy!

- The Apache Tomcat team

-
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org



svn commit: r1553692 - in /tomcat/site/trunk/docs/tomcat-8.0-doc: ./ WEB-INF/ api/ api/org/apache/catalina/ api/org/apache/catalina/ant/ api/org/apache/catalina/ant/jmx/ api/org/apache/catalina/authen

2013-12-27 Thread markt
Author: markt
Date: Fri Dec 27 16:38:37 2013
New Revision: 1553692

URL: http://svn.apache.org/r1553692
Log:
Update docs for 8.0.0-RC10 release


[This commit notification would consist of 80 parts, 
which exceeds the limit of 50 ones, so it was shortened to the summary.]

-
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org



svn commit: r1553705 - /tomcat/trunk/java/org/apache/catalina/webresources/mbeans-descriptors.xml

2013-12-27 Thread markt
Author: markt
Date: Fri Dec 27 17:44:12 2013
New Revision: 1553705

URL: http://svn.apache.org/r1553705
Log:
Align names between 7.0.x and 8.0.x (missed an mbean attribute)

Modified:
tomcat/trunk/java/org/apache/catalina/webresources/mbeans-descriptors.xml

Modified: 
tomcat/trunk/java/org/apache/catalina/webresources/mbeans-descriptors.xml
URL: 
http://svn.apache.org/viewvc/tomcat/trunk/java/org/apache/catalina/webresources/mbeans-descriptors.xml?rev=1553705&r1=1553704&r2=1553705&view=diff
==
--- tomcat/trunk/java/org/apache/catalina/webresources/mbeans-descriptors.xml 
(original)
+++ tomcat/trunk/java/org/apache/catalina/webresources/mbeans-descriptors.xml 
Fri Dec 27 17:44:12 2013
@@ -67,7 +67,7 @@
  type="long"
 writeable="true"/>
 
-



-
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org



Re: svn commit: r1553705 - /tomcat/trunk/java/org/apache/catalina/webresources/mbeans-descriptors.xml

2013-12-27 Thread Konstantin Kolinko
2013/12/27  :
> Author: markt
> Date: Fri Dec 27 17:44:12 2013
> New Revision: 1553705
>
> URL: http://svn.apache.org/r1553705
> Log:
> Align names between 7.0.x and 8.0.x (missed an mbean attribute)
>
> Modified:
> tomcat/trunk/java/org/apache/catalina/webresources/mbeans-descriptors.xml
>
> Modified: 
> tomcat/trunk/java/org/apache/catalina/webresources/mbeans-descriptors.xml
> URL: 
> http://svn.apache.org/viewvc/tomcat/trunk/java/org/apache/catalina/webresources/mbeans-descriptors.xml?rev=1553705&r1=1553704&r2=1553705&view=diff
> ==
> --- tomcat/trunk/java/org/apache/catalina/webresources/mbeans-descriptors.xml 
> (original)
> +++ tomcat/trunk/java/org/apache/catalina/webresources/mbeans-descriptors.xml 
> Fri Dec 27 17:44:12 2013
> @@ -67,7 +67,7 @@
>   type="long"
>  writeable="true"/>
>
> - +description="The maximum permitted size for a single object in the 
> cache in kB"
>   type="int"
>  writeable="true"/>


Searching for "maxObjectSize" (case-insensitively) the old name is
used in server-registry.xml  and twice in comments in Cache.java,
CachedResource.java:

File paths:
\java\org\apache\catalina\webresources\Cache.java
\java\org\apache\catalina\webresources\CachedResource.java
\java\org\apache\catalina\storeconfig\server-registry.xml

Best regards,
Konstantin Kolinko

-
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org



svn commit: r1553710 - in /tomcat/trunk/java/org/apache/catalina: storeconfig/server-registry.xml webresources/Cache.java webresources/CachedResource.java

2013-12-27 Thread markt
Author: markt
Date: Fri Dec 27 18:11:43 2013
New Revision: 1553710

URL: http://svn.apache.org/r1553710
Log:
Align names between 7.0.x and 8.0.x (more places - thanks to kkolinko)

Modified:
tomcat/trunk/java/org/apache/catalina/storeconfig/server-registry.xml
tomcat/trunk/java/org/apache/catalina/webresources/Cache.java
tomcat/trunk/java/org/apache/catalina/webresources/CachedResource.java

Modified: tomcat/trunk/java/org/apache/catalina/storeconfig/server-registry.xml
URL: 
http://svn.apache.org/viewvc/tomcat/trunk/java/org/apache/catalina/storeconfig/server-registry.xml?rev=1553710&r1=1553709&r2=1553710&view=diff
==
--- tomcat/trunk/java/org/apache/catalina/storeconfig/server-registry.xml 
(original)
+++ tomcat/trunk/java/org/apache/catalina/storeconfig/server-registry.xml Fri 
Dec 27 18:11:43 2013
@@ -258,7 +258,7 @@
 cachingAllowed
 cacheTTL
 cacheMaxSize
-cacheMaxObjectSize
+cacheObjectMaxSize
 cached
 caseSensitive
  

Modified: tomcat/trunk/java/org/apache/catalina/webresources/Cache.java
URL: 
http://svn.apache.org/viewvc/tomcat/trunk/java/org/apache/catalina/webresources/Cache.java?rev=1553710&r1=1553709&r2=1553710&view=diff
==
--- tomcat/trunk/java/org/apache/catalina/webresources/Cache.java (original)
+++ tomcat/trunk/java/org/apache/catalina/webresources/Cache.java Fri Dec 27 
18:11:43 2013
@@ -85,7 +85,7 @@ public class Cache {
 cacheEntry = newCacheEntry;
 cacheEntry.validate(useClassLoaderResources);
 
-// Even if the resource content larger than maxObjectSizeBytes
+// Even if the resource content larger than objectMaxSizeBytes
 // there is still benefit in caching the resource metadata
 
 long delta = cacheEntry.getSize();

Modified: tomcat/trunk/java/org/apache/catalina/webresources/CachedResource.java
URL: 
http://svn.apache.org/viewvc/tomcat/trunk/java/org/apache/catalina/webresources/CachedResource.java?rev=1553710&r1=1553709&r2=1553710&view=diff
==
--- tomcat/trunk/java/org/apache/catalina/webresources/CachedResource.java 
(original)
+++ tomcat/trunk/java/org/apache/catalina/webresources/CachedResource.java Fri 
Dec 27 18:11:43 2013
@@ -278,7 +278,7 @@ public class CachedResource implements W
 }
 
 // Assume that the cache entry will always include the content unless the
-// resource content is larger than maxObjectSizeBytes. This isn't always 
the
+// resource content is larger than objectMaxSizeBytes. This isn't always 
the
 // case but it makes tracking the current cache size easier.
 long getSize() {
 long result = CACHE_ENTRY_SIZE;



-
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org



Re: svn commit: r1553705 - /tomcat/trunk/java/org/apache/catalina/webresources/mbeans-descriptors.xml

2013-12-27 Thread Mark Thomas
On 27/12/2013 17:56, Konstantin Kolinko wrote:
> 2013/12/27  :
>> Author: markt
>> Date: Fri Dec 27 17:44:12 2013
>> New Revision: 1553705
>>
>> URL: http://svn.apache.org/r1553705
>> Log:
>> Align names between 7.0.x and 8.0.x (missed an mbean attribute)
>>
>> Modified:
>> tomcat/trunk/java/org/apache/catalina/webresources/mbeans-descriptors.xml
>>
>> Modified: 
>> tomcat/trunk/java/org/apache/catalina/webresources/mbeans-descriptors.xml
>> URL: 
>> http://svn.apache.org/viewvc/tomcat/trunk/java/org/apache/catalina/webresources/mbeans-descriptors.xml?rev=1553705&r1=1553704&r2=1553705&view=diff
>> ==
>> --- 
>> tomcat/trunk/java/org/apache/catalina/webresources/mbeans-descriptors.xml 
>> (original)
>> +++ 
>> tomcat/trunk/java/org/apache/catalina/webresources/mbeans-descriptors.xml 
>> Fri Dec 27 17:44:12 2013
>> @@ -67,7 +67,7 @@
>>   type="long"
>>  writeable="true"/>
>>
>> -> +>description="The maximum permitted size for a single object in 
>> the cache in kB"
>>   type="int"
>>  writeable="true"/>
> 
> 
> Searching for "maxObjectSize" (case-insensitively) the old name is
> used in server-registry.xml  and twice in comments in Cache.java,
> CachedResource.java:
> 
> File paths:
> \java\org\apache\catalina\webresources\Cache.java
> \java\org\apache\catalina\webresources\CachedResource.java
> \java\org\apache\catalina\storeconfig\server-registry.xml
> 
> Best regards,
> Konstantin Kolinko

Thanks. Fixed.

Mark


-
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org



Re: Support RFC6265 cookie processing

2013-12-27 Thread Jeremy Boynes
I think this is actually the principle that is the crux of the matter:
> With respect to the
> requirements of section 4.2, the Tomcat developers have always taken
> the view that cookie headers should be treated as "combinations of
> token, separators, and quoted-string" rather than "*TEXT" for the
> purposes of compliance with RFC2616. This view is rather fundamental
> to how cookies have been handled to date. 


Whilst I agree with the principle I think there are sufficient edge-cases in 
the ways user-agents and other servers handle cookies that trying to handle 
values by using RFC2109’s rules to avoid the need for handling “*TEXT” have 
resulted in some of the issues seen in the past. Simply put, a Netscape format 
Cookie header is not a combination of "token, separators, and quoted-string."

Part of this is that I have not seen widespread adoption of RFC2109 by 
user-agents. Instead, in the way they handle values they appear to accept 
RFC2109 format Set-Cookie headers from servers, process them in a 
Netscape-format manner, and then generate a Cookie header conforming to 
Netscape’s rules. Their RFC2109 support is primarily limited to attribute 
handing (e.g. allowing Max-Age or DQUOTE characters in Path (except IE)). They 
specifically don’t handle “Version” and don’t include the “$Version” attribute 
required by RFC2109 in the Cookie header.

Reviewing the “fun,” much of it can be attributed to presuming RFC2109 can be 
applied. For example, the fun around “=“ or “/“ characters, or the use of 
separator characters in unquoted values caused by trying to apply “token” rules 
to free text. Upgrading to RFC2109 to use quoted values is also an issue as 
user-agents are not parsing them as such; for example, Chrome-31 does not 
handle a quoted-string value per RFC2109:
  Set-Cookie:Customer="WILE_;_COYOTE"; Version="1"; Path="/"
instead treating it, loosely, as a Netscape-style value:
  Cookie:Customer="WILE_
Note, that value is not valid per RFC6265’s set-cookie-header rule but is per 
Netscape’s.

I think we can avoid this “fun” if we only apply RFC2109 rules to cookies that 
explicitly use version 1 (i.e. if setVersion(1) is called when setting a cookie 
or if $Version=“1” is present when parsing). For all others we would use 
RFC6265’s rules treating them as a less ambiguous version of Netscape’s syntax.

Whether that is actually true or not will depend on the behaviour we actually 
see from user-agents. With that in mind, I plan to start extending the tests to 
capture that behaviour so we have a clearer model of what is actually 
happening. That would then define what we need to do to ensure symmetry for the 
application developer and avoid the type of problem I mentioned above with 
Chrome. If that can be an incremental change then that would be ideal but that 
may not be possible if the change needed is to handle V0 and V1 cookies 
separately.

Cheers
Jeremy

On Dec 24, 2013, at 2:24 AM, Mark Thomas  wrote:

> Signed PGP part
> On 24/12/2013 01:21, Jeremy Boynes wrote:
> > In comments on issue #55917, there was suggestion for refactoring
> > cookie support along the lines described in RFC6265.
> 
> No, that isn't what I said. What I said was that now might be a good
> time to refactor the cookie parsing to use the HttpParser and that if
> we did that, that we should keep RFC6265 in mind. My intention was to
> suggest that if there were places where RFC6265 suggested relaxing the
> parsing rules and those rules could be relaxed without creating
> ambiguities or security concerns then we should consider such a change.
> 
> I also hinted at the 'fun' we have had with cookies in the past. I
> strongly recommend that you go and read all the various discussions
> and bug reports relating to cookie parsing.
> 
> In particular, the requirements of RFC2616 for HTTP headers were often
> overlooked.
> 
> > Reading this RFC, it appears to be more of an effort to standardize
> > the actual behaviour seen on the Internet for different browser and
> > server implementations. The observation is the RFC2109 has received
> > limited adoption and RFC2965 virtually none at all, with most
> > implementations falling back to the original specification released
> > by Netscape that contains certain ambiguities.
> 
> While I agree that RFC2965 has received little adoption, I disagree
> with the remainder. With the exception of internet explorer (and this
> might have changed in the few years since I last looked) the browsers
> all had pretty good support for RFC2109.
> 
> > The Servlet spec’s JavaDoc for Cookie refers to RFC2109 behaviour
> > with caveats around interoperability. It defines version 0 as
> > complying with Netscape’s original specification and version 1 as
> > complying RFC2109 (with the note “Since RFC 2109 is still somewhat
> > new, consider version 1 as experimental; do not use it yet on
> > production sites”).
> 
> That text is unchanged since at least Servlet 2.3 (12 years) so I
> wouldn't give it