Re: Servlet 3.1, Tomcat 8 etc.
On 27/07/2011 00:42, Konstantin Kolinko wrote: > 2011/7/26 Mark Thomas : >> The Servlet EG is starting to discuss changes to the Servlet API for >> 3.1. It would be useful if the option existed to implement some of these >> changes in Tomcat trunk. The benefits of this are: >> - we can see how feasible the API changes are to implement >> - users can try out the new APIs (assuming we do a Tomcat 8 alpha release) >> >> Therefore, after the next Tomcat 7 release, I would like to do the >> following: >> - Copy tomcat/trunk to tomcat/tc7.0.x/trunk >> - Start making Servlet API changes to tomcat/trunk > > Do you already have some changes on your mind? Nothing major at this point for the Servlet spec but I am expecting that to grow. The EL spec has also started discussing API changes that I'd like to implement. On the non-spec front, there is some refactoring of TLD/web.xml processing I'd like to do to reduce the duplication of both code and effort between Catalina and Jasper as well as some ideas I have for improving the performance a little bit. Mark - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
svn commit: r1151368 - /tomcat/jk/trunk/jkstatus/src/share/org/apache/jk/status/JkStatusUpdateWorkerTask.java
Author: jfclere
Date: Wed Jul 27 07:34:35 2011
New Revision: 1151368
URL: http://svn.apache.org/viewvc?rev=1151368&view=rev
Log:
According to mod_jk c code those command are now prefixed by v
Modified:
tomcat/jk/trunk/jkstatus/src/share/org/apache/jk/status/JkStatusUpdateWorkerTask.java
Modified:
tomcat/jk/trunk/jkstatus/src/share/org/apache/jk/status/JkStatusUpdateWorkerTask.java
URL:
http://svn.apache.org/viewvc/tomcat/jk/trunk/jkstatus/src/share/org/apache/jk/status/JkStatusUpdateWorkerTask.java?rev=1151368&r1=1151367&r2=1151368&view=diff
==
---
tomcat/jk/trunk/jkstatus/src/share/org/apache/jk/status/JkStatusUpdateWorkerTask.java
(original)
+++
tomcat/jk/trunk/jkstatus/src/share/org/apache/jk/status/JkStatusUpdateWorkerTask.java
Wed Jul 27 07:34:35 2011
@@ -242,31 +242,31 @@ public class JkStatusUpdateWorkerTask ex
sb.append("&sw=");
sb.append(URLEncoder.encode(worker, getCharset()));
if (loadfactor >= 0) {
- sb.append("&wf=");
+ sb.append("&vwf=");
sb.append(loadfactor);
}
if (route != null) {
- sb.append("&wn=");
+ sb.append("&vwn=");
sb.append(URLEncoder.encode(route,
getCharset()));
}
if (activation == null && activationCode > 0 &&
activationCode < 4) {
- sb.append("&wa=");
+ sb.append("&vwa=");
sb.append(activation);
}
if (activation != null) {
- sb.append("&wa=");
+ sb.append("&vwa=");
sb.append(URLEncoder.encode(activation,
getCharset()));
}
if (distance >= 0) {
- sb.append("&wd=");
+ sb.append("&vwd=");
sb.append(distance);
}
if (redirect != null) { // other worker conrecte lb's
- sb.append("&wr=");
+ sb.append("&vwr=");
sb.append(URLEncoder.encode(redirect,
getCharset()));
}
if (domain != null) {
- sb.append("&wc=");
+ sb.append("&vwc=");
sb.append(URLEncoder.encode(domain,
getCharset()));
}
@@ -288,4 +288,4 @@ public class JkStatusUpdateWorkerTask ex
throw new BuildException("Must specify 'loadbalancer' attribute");
}
}
-}
\ No newline at end of file
+}
-
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org
svn commit: r1151374 - /tomcat/native/tags/TOMCAT_NATIVE_1_1_21/
Author: jfclere Date: Wed Jul 27 08:11:04 2011 New Revision: 1151374 URL: http://svn.apache.org/viewvc?rev=1151374&view=rev Log: tag for the release 1.1.21 Added: tomcat/native/tags/TOMCAT_NATIVE_1_1_21/ (props changed) - copied from r1151373, tomcat/native/branches/1.1.x/ Propchange: tomcat/native/tags/TOMCAT_NATIVE_1_1_21/ -- --- svn:ignore (added) +++ svn:ignore Wed Jul 27 08:11:04 2011 @@ -0,0 +1 @@ +dist Propchange: tomcat/native/tags/TOMCAT_NATIVE_1_1_21/ -- svn:mergeinfo = /tomcat/native/trunk:815411 - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
svn commit: r1151389 - /tomcat/trunk/webapps/docs/windows-auth-howto.xml
Author: markt Date: Wed Jul 27 08:55:02 2011 New Revision: 1151389 URL: http://svn.apache.org/viewvc?rev=1151389&view=rev Log: This is now available Modified: tomcat/trunk/webapps/docs/windows-auth-howto.xml Modified: tomcat/trunk/webapps/docs/windows-auth-howto.xml URL: http://svn.apache.org/viewvc/tomcat/trunk/webapps/docs/windows-auth-howto.xml?rev=1151389&r1=1151388&r2=1151389&view=diff == --- tomcat/trunk/webapps/docs/windows-auth-howto.xml (original) +++ tomcat/trunk/webapps/docs/windows-auth-howto.xml Wed Jul 27 08:55:02 2011 @@ -41,7 +41,7 @@ part of the domain. There are several options for implementing integrated Windows authentication with Apache Tomcat. They are: -Built-in Tomcat support (work in progress, not yet available). +Built-in Tomcat support. Use a third party library such as Waffle. Use a reverse proxy that supports Windows authentication to perform the authentication step such as IIS or httpd. - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
svn commit: r1151395 - in /tomcat/trunk/webapps/docs: changelog.xml realm-howto.xml
Author: markt
Date: Wed Jul 27 09:13:36 2011
New Revision: 1151395
URL: http://svn.apache.org/viewvc?rev=1151395&view=rev
Log:
Fix https://issues.apache.org/bugzilla/show_bug.cgi?id=51561
Recommend the use of digest.[bat|sh] to generate digests rather than calling
RealmBase directly.
Modified:
tomcat/trunk/webapps/docs/changelog.xml
tomcat/trunk/webapps/docs/realm-howto.xml
Modified: tomcat/trunk/webapps/docs/changelog.xml
URL:
http://svn.apache.org/viewvc/tomcat/trunk/webapps/docs/changelog.xml?rev=1151395&r1=1151394&r2=1151395&view=diff
==
--- tomcat/trunk/webapps/docs/changelog.xml (original)
+++ tomcat/trunk/webapps/docs/changelog.xml Wed Jul 27 09:13:36 2011
@@ -158,6 +158,11 @@
the implications of setting the path attribute on a Context element in
server.xml. (markt)
+
+51561: Update the Realm page within the documentation web
+application to recommend the use of digest.[bat|sh] to generate digests
+rather than calling RealmBase directly. (markt)
+
Modified: tomcat/trunk/webapps/docs/realm-howto.xml
URL:
http://svn.apache.org/viewvc/tomcat/trunk/webapps/docs/realm-howto.xml?rev=1151395&r1=1151394&r2=1151395&view=diff
==
--- tomcat/trunk/webapps/docs/realm-howto.xml (original)
+++ tomcat/trunk/webapps/docs/realm-howto.xml Wed Jul 27 09:13:36 2011
@@ -196,9 +196,7 @@ techniques are supported:
method will return the digested password.
If you want to execute a command line utility to calculate the digested
password, simply execute
-
-java org.apache.catalina.realm.RealmBase \
--a {algorithm} {cleartext-password}
+CATALINA_HOME/bin/digest.[bat|sh] -a {algorithm} {cleartext-password}
and the digested version of this cleartext password will be returned to
standard output.
@@ -215,19 +213,8 @@ java org.apache.catalina.realm.RealmBase
not specified in web.xml, the default value of Authentication
required is used.
-To use either of the above techniques, the following jar files will need
-to be on your class path to make the RealmBase class available:
-
-
-
- $CATALINA_HOME/bin/tomcat-juli.jar
- $CATALINA_HOME/lib/catalina.jar
- $CATALINA_HOME/lib/tomcat-util.jar
-
-
Non-ASCII usernames and/or passwords are supported using
-java org.apache.catalina.realm.RealmBase \
--a {algorithm} -e {encoding} {input}
+CATALINA_HOME/bin/digest.[bat|sh] -a {algorithm} -e {encoding} {input}
but care is required to ensure that the non-ASCII input is
correctly passed to the digester.
-
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org
DO NOT REPLY [Bug 51557] Newline during a http header field name obscures next value
https://issues.apache.org/bugzilla/show_bug.cgi?id=51557 Mark Thomas changed: What|Removed |Added Status|NEW |RESOLVED Resolution||FIXED --- Comment #2 from Mark Thomas 2011-07-27 09:10:43 UTC --- This has been fixed in 7.0.x and will be included in 7.0.20 onwards. -- Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
svn commit: r1151394 - in /tomcat/trunk: java/org/apache/coyote/http11/ test/org/apache/coyote/http11/ webapps/docs/
Author: markt
Date: Wed Jul 27 09:10:11 2011
New Revision: 1151394
URL: http://svn.apache.org/viewvc?rev=1151394&view=rev
Log:
Fix https://issues.apache.org/bugzilla/show_bug.cgi?id=51557
Ignore HTTP headers that do not comply with RFC 2616 and use header names that
are not tokens.
Modified:
tomcat/trunk/java/org/apache/coyote/http11/AbstractInputBuffer.java
tomcat/trunk/java/org/apache/coyote/http11/InternalAprInputBuffer.java
tomcat/trunk/java/org/apache/coyote/http11/InternalInputBuffer.java
tomcat/trunk/java/org/apache/coyote/http11/InternalNioInputBuffer.java
tomcat/trunk/java/org/apache/coyote/http11/LocalStrings.properties
tomcat/trunk/test/org/apache/coyote/http11/TestInternalInputBuffer.java
tomcat/trunk/webapps/docs/changelog.xml
Modified: tomcat/trunk/java/org/apache/coyote/http11/AbstractInputBuffer.java
URL:
http://svn.apache.org/viewvc/tomcat/trunk/java/org/apache/coyote/http11/AbstractInputBuffer.java?rev=1151394&r1=1151393&r2=1151394&view=diff
==
--- tomcat/trunk/java/org/apache/coyote/http11/AbstractInputBuffer.java
(original)
+++ tomcat/trunk/java/org/apache/coyote/http11/AbstractInputBuffer.java Wed Jul
27 09:10:11 2011
@@ -27,20 +27,7 @@ import org.apache.tomcat.util.res.String
public abstract class AbstractInputBuffer implements InputBuffer{
-public abstract boolean parseRequestLine(boolean useAvailableDataOnly)
throws IOException;
-
-public abstract boolean parseHeaders() throws IOException;
-
-protected abstract boolean fill(boolean block) throws IOException;
-
-// -- Constants
-
-
-// --- Constructors
-
-
-// -- Variables
-
+protected static final boolean[] HTTP_TOKEN_CHAR = new boolean[128];
/**
* The string manager for this package.
@@ -49,7 +36,55 @@ public abstract class AbstractInputBuffe
StringManager.getManager(Constants.Package);
-// - Instance Variables
+static {
+for (int i = 0; i < 128; i++) {
+if (i < 32) {
+HTTP_TOKEN_CHAR[i] = false;
+} else if (i == 127) {
+HTTP_TOKEN_CHAR[i] = false;
+} else if (i == '(') {
+HTTP_TOKEN_CHAR[i] = false;
+} else if (i == ')') {
+HTTP_TOKEN_CHAR[i] = false;
+} else if (i == '<') {
+HTTP_TOKEN_CHAR[i] = false;
+} else if (i == '>') {
+HTTP_TOKEN_CHAR[i] = false;
+} else if (i == '@') {
+HTTP_TOKEN_CHAR[i] = false;
+} else if (i == ',') {
+HTTP_TOKEN_CHAR[i] = false;
+} else if (i == ';') {
+HTTP_TOKEN_CHAR[i] = false;
+} else if (i == ':') {
+HTTP_TOKEN_CHAR[i] = false;
+} else if (i == '\\') {
+HTTP_TOKEN_CHAR[i] = false;
+} else if (i == '\"') {
+HTTP_TOKEN_CHAR[i] = false;
+} else if (i == '/') {
+HTTP_TOKEN_CHAR[i] = false;
+} else if (i == '[') {
+HTTP_TOKEN_CHAR[i] = false;
+} else if (i == ']') {
+HTTP_TOKEN_CHAR[i] = false;
+} else if (i == '?') {
+HTTP_TOKEN_CHAR[i] = false;
+} else if (i == '=') {
+HTTP_TOKEN_CHAR[i] = false;
+} else if (i == '{') {
+HTTP_TOKEN_CHAR[i] = false;
+} else if (i == '}') {
+HTTP_TOKEN_CHAR[i] = false;
+} else if (i == ' ') {
+HTTP_TOKEN_CHAR[i] = false;
+} else if (i == '\t') {
+HTTP_TOKEN_CHAR[i] = false;
+} else {
+HTTP_TOKEN_CHAR[i] = true;
+}
+}
+}
/**
@@ -217,6 +252,13 @@ public abstract class AbstractInputBuffe
}
+public abstract boolean parseRequestLine(boolean useAvailableDataOnly)
throws IOException;
+
+public abstract boolean parseHeaders() throws IOException;
+
+protected abstract boolean fill(boolean block) throws IOException;
+
+
// - Public Methods
@@ -308,6 +350,4 @@ public abstract class AbstractInputBuffe
return activeFilters[lastActiveFilter].doRead(chunk,req);
}
-
-
}
Modified: tomcat/trunk/java/org/apache/coyote/http11/InternalAprInputBuffer.java
URL:
http://svn.apache.org/viewvc/tomcat/trunk/java/org/apache/coyote/http11/InternalAprInputBuffer.java?rev=1151394&r1=1151393&r2=1151394&view=diff
==
--- tomcat/trunk/java/org/apache/coyo
DO NOT REPLY [Bug 51561] Missing tomcat-coyote.jar from classpath requirement on Realm HowTo page, digested passwords section
https://issues.apache.org/bugzilla/show_bug.cgi?id=51561 Mark Thomas changed: What|Removed |Added Status|NEW |RESOLVED Resolution||FIXED --- Comment #3 from Mark Thomas 2011-07-27 09:13:49 UTC --- This has been fixed in 7.0.x and will be included in 7.0.20 onwards. -- Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
[VOTE] Release Apache Tomcat Native 1.1.21
Hi, Native 1.1.21 is available for testing. Compared with 1.1.21 and earlier versions it fixes some bugs. If you want to take a look, the final source distribution can be downloaded from: http://tomcat.apache.org/dev/dist/tomcat-connectors/native/1.1.21/source (Will be visible after the server sync is done) Win32/Win64 binaries will be available at: http://tomcat.apache.org/dev/dist/tomcat-connectors/native/1.1.21/binaries/ So here's the vote. It will be closed in about 72 hours (or sooner if enough votes are encountered) Apache Tomcat Native 1.1.21 is: [ ] Stable - no major issues, no regressions [ ] Beta - at least one significant issue -- tell us what it is [ ] Alpha - multiple significant issues -- tell us what they are Cheers Jean-Frederic - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
DO NOT REPLY [Bug 49591] Custom error page always uses Transfer-Encoding: chunked
https://issues.apache.org/bugzilla/show_bug.cgi?id=49591 Mark Thomas changed: What|Removed |Added Status|NEW |RESOLVED Resolution||WONTFIX --- Comment #3 from Mark Thomas 2011-07-27 09:47:01 UTC --- I agree with Tim. -- Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
svn commit: r1151408 - in /tomcat/trunk/java/org/apache/catalina: ha/tcp/LocalStrings.properties ha/tcp/LocalStrings_es.properties tribes/transport/LocalStrings.properties tribes/transport/LocalString
Author: kfujino
Date: Wed Jul 27 09:58:20 2011
New Revision: 1151408
URL: http://svn.apache.org/viewvc?rev=1151408&view=rev
Log:
Correct LocalStrings.properties.
Some invalid messagekeys are removed.
e.g.
remove AsyncSocketSender.XXX and FastAsyncSocketSender.XXX keys.
ReplicationValve.XXX and SimpleTcpCluster.XX are removed from
org.apache.catalina.tribes.transport.LocalStrings.properties.
Modified:
tomcat/trunk/java/org/apache/catalina/ha/tcp/LocalStrings.properties
tomcat/trunk/java/org/apache/catalina/ha/tcp/LocalStrings_es.properties
tomcat/trunk/java/org/apache/catalina/tribes/transport/LocalStrings.properties
tomcat/trunk/java/org/apache/catalina/tribes/transport/LocalStrings_es.properties
Modified: tomcat/trunk/java/org/apache/catalina/ha/tcp/LocalStrings.properties
URL:
http://svn.apache.org/viewvc/tomcat/trunk/java/org/apache/catalina/ha/tcp/LocalStrings.properties?rev=1151408&r1=1151407&r2=1151408&view=diff
==
--- tomcat/trunk/java/org/apache/catalina/ha/tcp/LocalStrings.properties
(original)
+++ tomcat/trunk/java/org/apache/catalina/ha/tcp/LocalStrings.properties Wed
Jul 27 09:58:20 2011
@@ -13,43 +13,6 @@
# See the License for the specific language governing permissions and
# limitations under the License.
-AsyncSocketSender.create.thread=Create sender [{0}:{1,number,integer}] queue
thread to tcp background replication
-AsyncSocketSender.queue.message=Queue message to [{0}:{1,number,integer}]
id=[{2}] size={3}
-AsyncSocketSender.send.error=Unable to asynchronously send session with
id=[{0}] - message will be ignored.
-AsyncSocketSender.queue.empty=Queue in sender [{0}:{1,number,integer}]
returned null element!
-cluster.mbean.register.already=MBean {0} already registered!
-FastAsyncSocketSender.setThreadPriority=[{0}:{1,number,integer}] set priority
to {2}
-FastAsyncSocketSender.min.exception=[{0}:{1,number,integer}] new priority {2}
< MIN_PRIORITY
-FastAsyncSocketSender.max.exception=[{0}:{1,number,integer}] new priority {2}
> MAX_PRIORITY
-IDataSender.ack.eof=EOF reached at local port [{0}:{1,number,integer}]
-IDataSender.ack.receive=Got ACK at local port [{0}:{1,number,integer}]
-IDataSender.ack.missing=Unable to read acknowledgement from
[{0}:{1,number,integer}] in {2,number,integer} ms. Disconnecting socket, and
trying again.
-IDataSender.ack.read=Read wait ack char '{2}' [{0}:{1,number,integer}]
-IDataSender.ack.start=Waiting for ACK message [{0}:{1,number,integer}]
-IDataSender.ack.wrong=Missing correct ACK after 10 bytes read at local port
[{0}:{1,number,integer}]
-IDataSender.closeSocket=Sender close socket to [{0}:{1,number,integer}] (close
count {2,number,integer})
-IDataSender.connect=Sender connect to [{0}:{1,number,integer}] (connect count
{2,number,integer})
-IDataSender.create=Create sender [{0}:{1,number,integer}]
-IDataSender.disconnect=Sender disconnect from [{0}:{1,number,integer}]
(disconnect count {2,number,integer})
-IDataSender.message.disconnect=Message transfered: Sender can't disconnect
from [{0}:{1,number,integer}]
-IDataSender.message.create=Message transfered: Sender can't create current
socket [{0}:{1,number,integer}]
-IDataSender.openSocket=Sender open socket to [{0}:{1,number,integer}] (open
count {2,number,integer})
-IDataSender.openSocket.failure=Open sender socket [{0}:{1,number,integer}]
failure! (open failure count {2,number,integer})
-IDataSender.send.again=Send data again to [{0}:{1,number,integer}]
-IDataSender.send.crash=Send message crashed [{0}:{1,number,integer}]
type=[{2}], id=[{3}]
-IDataSender.send.message=Send message to [{0}:{1,number,integer}] id=[{2}]
size={3,number,integer}
-IDataSender.send.lost=Message lost: [{0}:{1,number,integer}] type=[{2}],
id=[{3}]
-IDataSender.senderModes.Configured=Configured a data replication sender for
mode {0}
-IDataSender.senderModes.Instantiate=Can't instantiate a data replication
sender of class {0}
-IDataSender.senderModes.Missing=Can't configure a data replication sender for
mode {0}
-IDataSender.senderModes.Resources=Can't load data replication sender mapping
list
-IDataSender.stats=Send stats from [{0}:{1,number,integer}], Nr of bytes
sent={2,number,integer} over {3} = {4,number,integer} bytes/request, processing
time {5,number,integer} msec, avg processing time {6,number,integer} msec
-PoolSocketSender.senderQueue.sender.failed=PoolSocketSender create new sender
to [{0}:{1,number,integer}] failed
-PoolSocketSender.noMoreSender=No socket sender available for client
[{0}:{1,number,integer}] did it disappeared?
-ReplicationTransmitter.getProperty=get property {0}
-ReplicationTransmitter.setProperty=set property {0}: {1} old value {2}
-ReplicationTransmitter.started=Start ClusterSender at cluster {0} with name {1}
-ReplicationTransmitter.stopped=Stopped ClusterSender at cluster {0} with name
{1}
ReplicationValve.crossContext.add=add Cross Context session replication
con
Re: Servlet 3.1, Tomcat 8 etc.
+1 To getting newer ideas in faster. I guess the question to ponder is what are the future changes pending for 7? What are the changes for the servlet spec? I have a feeling that the servlet spec changes are more of a playground for ideas which would bring about lots of change and potential reversions. With that in mind - it seems like it belongs in the sandbox. But sandbox might imply a private playground or its a ghetto (american slang) area of the repository that only the brave should wander into. So to test servlet spec changes, would it be better to create a branch called servlet3.1 so if new ideas come into trunk - they might not conflict for servlet 3.1 concepts? Then once servlet 3.1 goes into public review (or some similar status) - then the changes get merged back into trunk and tomcat7 gets its own branch? -Tim On Tue, Jul 26, 2011 at 1:30 PM, Mark Thomas wrote: > The Servlet EG is starting to discuss changes to the Servlet API for > 3.1. It would be useful if the option existed to implement some of these > changes in Tomcat trunk. The benefits of this are: > - we can see how feasible the API changes are to implement > - users can try out the new APIs (assuming we do a Tomcat 8 alpha release) > > Therefore, after the next Tomcat 7 release, I would like to do the > following: > - Copy tomcat/trunk to tomcat/tc7.0.x/trunk > - Start making Servlet API changes to tomcat/trunk > > Assuming that there are no objections to that plan, that leads to a > couple of other questions. > > 1. Should tomcat/tc7.0.x/trunk be RTC or CTR? > > 2. With tomcat/trunk becoming the basis for Tomcat 8, I would like to > see earlier and more frequent alpha/beta releases than we had for Tomcat > 7. That would increase the effective number of versions we are > supporting. With that in mind, should we announce end of support for > 5.5.x with the last release expected in ~12 months time? > >
Re: [VOTE] Release Apache Tomcat Native 1.1.21
On 07/27/2011 11:20 AM, jean-frederic clere wrote: Win32/Win64 binaries will be available at: http://tomcat.apache.org/dev/dist/tomcat-connectors/native/1.1.21/binaries/ Think we should stop shipping anything that is not voted for. You should have call for a vote after the binaries are uploaded. Otherwise we would need a new vote for the binaries. Cheers -- ^TM - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
svn commit: r1151444 - in /tomcat/trunk/webapps: ROOT/index.jsp ROOT/tomcat.css docs/changelog.xml
Author: markt
Date: Wed Jul 27 12:23:28 2011
New Revision: 1151444
URL: http://svn.apache.org/viewvc?rev=1151444&view=rev
Log:
Fix https://issues.apache.org/bugzilla/show_bug.cgi?id=49122
Layout improvements and tweaks
Modified:
tomcat/trunk/webapps/ROOT/index.jsp
tomcat/trunk/webapps/ROOT/tomcat.css
tomcat/trunk/webapps/docs/changelog.xml
Modified: tomcat/trunk/webapps/ROOT/index.jsp
URL:
http://svn.apache.org/viewvc/tomcat/trunk/webapps/ROOT/index.jsp?rev=1151444&r1=1151443&r2=1151444&view=diff
==
--- tomcat/trunk/webapps/ROOT/index.jsp (original)
+++ tomcat/trunk/webapps/ROOT/index.jsp Wed Jul 27 12:23:28 2011
@@ -21,6 +21,7 @@ java.text.SimpleDateFormat sdf = new jav
request.setAttribute("year", sdf.format(new java.util.Date()));
request.setAttribute("tomcat7Url", "http://tomcat.apache.org/";);
request.setAttribute("tomcat7DocUrl", "/docs/");
+request.setAttribute("tomcat7ExamplesUrl", "/examples/");
%>
@@ -35,20 +36,15 @@ request.setAttribute("tomcat7DocUrl", "/
Home
Documentation
-Configuration
+Configuration
+Examples
http://wiki.apache.org/tomcat/FrontPage";>Wiki
Mailing
Lists
Find
Help
-
-<%=request.getServletContext().getServerInfo() %>
-
-
-http://www.apache.org/";>
-
-
+${pageContext.servletContext.serverInfo}
@@ -95,8 +91,8 @@ request.setAttribute("tomcat7DocUrl", "/
-Servlet
Examples
-JSP Examples
+Servlet
Examples
+JSP
Examples
@@ -114,14 +110,13 @@ request.setAttribute("tomcat7DocUrl", "/
For security, access to the manager webapp is restricted.
Users are defined in:
$CATALINA_HOME/conf/tomcat-users.xml
-In Tomcat 7.0 access to the manager application is
split between different users.
-Read
more...
+In Tomcat 7.0 access to the manager application is
split between
+ different users. Read more...
Release Notes
Changelog
Migration
Guide
-Security
Updates
-
+Security
Notices
@@ -137,15 +132,13 @@ request.setAttribute("tomcat7DocUrl", "/
https://issues.apache.org/bugzilla/buglist.cgi?bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_status=RESOLVED&resolution=LATER&resolution=REMIND&resolution=---&bugidtype=include&product=Tomcat+7&cmdtype=doit&order=Importance";>Tomcat
7.0 Bug Database
Tomcat 7.0 JavaDocs
http://svn.apache.org/repos/asf/tomcat/tc7.0.x/";>Tomcat 7.0 SVN
Repository
-Tomcat 7.0
Examples
Getting Help
-FAQ
-Mailing
Lists
+FAQ and Mailing Lists
The following mailing lists are available:
mailto:announce-subscr...@tomcat.apache.org";>annou...@tomcat.apache.org
Modified: tomcat/trunk/webapps/ROOT/tomcat.css
URL:
http://svn.apache.org/viewvc/tomcat/trunk/webapps/ROOT/tomcat.css?rev=1151444&r1=1151443&r2=1151444&view=diff
==
--- tomcat/trunk/webapps/ROOT/tomcat.css (original)
+++ tomcat/trunk/webapps/ROOT/tomcat.css Wed Jul 27 12:23:28 2011
@@ -128,25 +128,12 @@ a img {
}
#asf-box {
-padding: 0 20px;
-margin: 0 0 20px;
-text-align: left;
-}
-
-#version {
-padding: 6px top left;
-float: left;
-width: 30%;
-}
-#version h2 {
+height: 40px;
+background: #fff url(asf-logo.png) no-repeat top right;}
+#asf-box h1 {
padding: 0;
margin: 0;
}
-#upper-asf {
-float: right;
-width: 60%;
-text-align: right;
-}
#upper {
background: #fff url(bg-upper.png) repeat-x top left;
@@ -290,10 +277,10 @@ a img {
#lower li {
font-size: 9pt;
color: #753;
-margin: 0 0 0.25em;
+margin: 0 0 0.1em;
}
#lower li {
-padding: 5px;
+padding: 3px 5px;
}
#lower li
DO NOT REPLY [Bug 49122] Update of ROOT application index.html
https://issues.apache.org/bugzilla/show_bug.cgi?id=49122 Mark Thomas changed: What|Removed |Added Status|REOPENED|RESOLVED Resolution||FIXED --- Comment #10 from Mark Thomas 2011-07-27 12:23:51 UTC --- Thanks. Tweaks applied with minor modifications. -- Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
Re: Servlet 3.1, Tomcat 8 etc.
Meta: +1 to starting this thread and its thinking this early. On Tue, Jul 26, 2011 at 1:30 PM, Mark Thomas wrote: > Therefore, after the next Tomcat 7 release, I would like to do the > following: > - Copy tomcat/trunk to tomcat/tc7.0.x/trunk > - Start making Servlet API changes to tomcat/trunk +1. > > Assuming that there are no objections to that plan, that leads to a > couple of other questions. > > 1. Should tomcat/tc7.0.x/trunk be RTC or CTR? CTR for now. > 2. With tomcat/trunk becoming the basis for Tomcat 8, I would like to > see earlier and more frequent alpha/beta releases than we had for Tomcat > 7. That would increase the effective number of versions we are > supporting. With that in mind, should we announce end of support for > 5.5.x with the last release expected in ~12 months time? +1. Yoav - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
Re: Servlet 3.1, Tomcat 8 etc.
2011/7/27 Mark Thomas : > The Servlet EG is starting to discuss changes to the Servlet API for > 3.1. It would be useful if the option existed to implement some of these > changes in Tomcat trunk. The benefits of this are: > - we can see how feasible the API changes are to implement > - users can try out the new APIs (assuming we do a Tomcat 8 alpha release) > > Therefore, after the next Tomcat 7 release, I would like to do the > following: > - Copy tomcat/trunk to tomcat/tc7.0.x/trunk > - Start making Servlet API changes to tomcat/trunk > +1 > Assuming that there are no objections to that plan, that leads to a > couple of other questions. > > 1. Should tomcat/tc7.0.x/trunk be RTC or CTR? > CTR > 2. With tomcat/trunk becoming the basis for Tomcat 8, I would like to > see earlier and more frequent alpha/beta releases than we had for Tomcat > 7. That would increase the effective number of versions we are > supporting. With that in mind, should we announce end of support for > 5.5.x with the last release expected in ~12 months time? > +1 -- Keiichi.Fujino - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
svn commit: r1151493 - in /tomcat/trunk/webapps/docs: changelog.xml ssl-howto.xml
Author: markt
Date: Wed Jul 27 15:11:35 2011
New Revision: 1151493
URL: http://svn.apache.org/viewvc?rev=1151493&view=rev
Log:
Fix https://issues.apache.org/bugzilla/show_bug.cgi?id=48997
Fixed some typos and correct cross-referencing to the HTTP Connector
documentation with the SSL How-To page of the documentation web application.
Modified:
tomcat/trunk/webapps/docs/changelog.xml
tomcat/trunk/webapps/docs/ssl-howto.xml
Modified: tomcat/trunk/webapps/docs/changelog.xml
URL:
http://svn.apache.org/viewvc/tomcat/trunk/webapps/docs/changelog.xml?rev=1151493&r1=1151492&r2=1151493&view=diff
==
--- tomcat/trunk/webapps/docs/changelog.xml (original)
+++ tomcat/trunk/webapps/docs/changelog.xml Wed Jul 27 15:11:35 2011
@@ -142,6 +142,11 @@
configuration page in the documentation web application. (markt)
+48997: Fixed some typos and correct cross-referencing to the
+HTTP Connector documentation with the SSL How-To page of the
+documentation web application. (markt)
+
+
49122: Improvements and fixes for index page for ROOT web
application. Based on a patch provided by pidster. (markt)
Modified: tomcat/trunk/webapps/docs/ssl-howto.xml
URL:
http://svn.apache.org/viewvc/tomcat/trunk/webapps/docs/ssl-howto.xml?rev=1151493&r1=1151492&r2=1151493&view=diff
==
--- tomcat/trunk/webapps/docs/ssl-howto.xml (original)
+++ tomcat/trunk/webapps/docs/ssl-howto.xml Wed Jul 27 15:11:35 2011
@@ -47,7 +47,8 @@
To install and configure SSL support on Tomcat, you need to follow
these simple steps. For more information, read the rest of this HOW-TO.
-Create a certificate keystore by executing the following command:
+Create a certificate keystore file to store the servers private key and
+self-signed certificate by executing the following command:
Windows:
%JAVA_HOME%\bin\keytool -genkey -alias tomcat -keyalg RSA
@@ -370,13 +371,16 @@ file installed with Tomcat. For JSSE, i
-You will note that the Connector element itself is commented out by default,
-so you will need to remove the comment tags around it. Then, you can
-customize the specified attributes as necessary. For detailed information
-about the various options, consult the
-Server Configuration Reference. The
-following discussion covers only those attributes of most interest when
-setting up SSL communication.
+You will note that the example SSL connector elements are commented out by
+default. You can either remove the comment tags from around the the example SSL
+connector you wish to use or add a new Connector element of your own. In either
+case, you will need to configure the SSL Connector for your requirements
+and environment. The configuration options and information on which attributes
+are mandatory, are documented in the SSL Support section of the
+HTTP connector configuration
+reference. Make sure that you use the correct attributes for the connector you
+are using. The BIO and NIO connectors use JSSE whereas the APR/native connector
+uses APR.
The port attribute (default value is 8443) is the TCP/IP
port number on which Tomcat will listen for secure connections. You can
@@ -393,22 +397,12 @@ numbers lower than 1024 on many operatin
that SSL is required, as required by the Servlet Specification.
-There are additional options used to configure the SSL protocol. You may
-need to add or change some attributes, depending on how you configured your
-keystore earlier. If you are using a Java JSSE based SSL connector then
-configuration options are documented in the
-Java HTTP connector configuration
-reference. If you are using the APR/native connector then refer to the
-APR connector configuration guide for details of the
-available configuration options.
-
After completing these configuration changes, you must restart Tomcat as
you normally do, and you should be in business. You should be able to access
any web application supported by Tomcat via SSL. For example, try:
https://localhost:8443
-
and you should see the usual Tomcat splash page (unless you have modified
the ROOT web application). If this does not work, the following section
contains some troubleshooting tips.
@@ -477,13 +471,6 @@ SSL communications, and what to do about
-I get "java.security.NoSuchAlgorithmException" errors in my
-log files.
-
-The JVM cannot find the JSSE JAR files. Follow all of the directions to
-download and install JSSE.
-
-
When Tomcat starts up, I get an exception like
"java.io.FileNotFoundException: {some-directory}/{some-file} not found".
@@ -518,7 +505,7 @@ SSL communications, and what to do about
enabled."
A likely explanation is that Tomcat cannot find the alias for the server
-key withinthe specified keystore. Check that the co
DO NOT REPLY [Bug 51562] two key's value is mistake in "org/apache/catalina/connector/LocalStrings.properties"
https://issues.apache.org/bugzilla/show_bug.cgi?id=51562 --- Comment #2 from gu lilan 2011-07-27 15:13:08 UTC --- yes,i see ,thank you -- Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
DO NOT REPLY [Bug 48997] enhance ssl-howto documentation
https://issues.apache.org/bugzilla/show_bug.cgi?id=48997 --- Comment #3 from Mark Thomas 2011-07-27 15:24:33 UTC --- The following changes have been made in 7.0.x and will be included in 7.0.20 onwards: 1 - added explanatory test to the quick start section 2 - fixed 3 - improved cross-reference to configuration no changes to trouble shooting (want to keep that to common issues) I also fixed some other issues in the docs. -- Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
Re: Servlet 3.1, Tomcat 8 etc.
On 07/26/2011 07:30 PM, Mark Thomas wrote: 1. Should tomcat/tc7.0.x/trunk be RTC or CTR? CTR 2. With tomcat/trunk becoming the basis for Tomcat 8, I would like to see earlier and more frequent alpha/beta releases than we had for Tomcat Sure. This time we might have 8 ready as 3.1 spec is defined. I have no problem if it's bound to spec RC cause it won't be stable until 3.1 spec is frozen. 7. That would increase the effective number of versions we are supporting. With that in mind, should we announce end of support for 5.5.x with the last release expected in ~12 months time? After we release first 8 stable or starting from now? Regards -- ^TM - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
Tomcat 6.0.33 ?
Hi guys, We're stuck with Tomcat 6.0.32 with this bug (https://issues.apache.org/bugzilla/show_bug.cgi?id=50189). Did there is any date for 6.0.33 release ? Regards - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
Re: Servlet 3.1, Tomcat 8 etc.
On 27/07/2011 16:48, Mladen Turk wrote: > On 07/26/2011 07:30 PM, Mark Thomas wrote: >> >> 1. Should tomcat/tc7.0.x/trunk be RTC or CTR? >> > > CTR > > >> 2. With tomcat/trunk becoming the basis for Tomcat 8, I would like to >> see earlier and more frequent alpha/beta releases than we had for Tomcat > > Sure. This time we might have 8 ready as 3.1 spec is defined. > I have no problem if it's bound to spec RC cause it won't be > stable until 3.1 spec is frozen. > >> 7. That would increase the effective number of versions we are >> supporting. With that in mind, should we announce end of support for >> 5.5.x with the last release expected in ~12 months time? >> > > After we release first 8 stable or starting from now? I was thinking announce EOL for 5.5.x now, with the actual EOL date / last release ~August 2012. Mark - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
svn commit: r1151532 - /tomcat/trunk/webapps/docs/ssl-howto.xml
Author: markt Date: Wed Jul 27 16:58:36 2011 New Revision: 1151532 URL: http://svn.apache.org/viewvc?rev=1151532&view=rev Log: Typo Modified: tomcat/trunk/webapps/docs/ssl-howto.xml Modified: tomcat/trunk/webapps/docs/ssl-howto.xml URL: http://svn.apache.org/viewvc/tomcat/trunk/webapps/docs/ssl-howto.xml?rev=1151532&r1=1151531&r2=1151532&view=diff == --- tomcat/trunk/webapps/docs/ssl-howto.xml (original) +++ tomcat/trunk/webapps/docs/ssl-howto.xml Wed Jul 27 16:58:36 2011 @@ -47,7 +47,7 @@ To install and configure SSL support on Tomcat, you need to follow these simple steps. For more information, read the rest of this HOW-TO. -Create a certificate keystore file to store the servers private key and +Create a keystore file to store the server's private key and self-signed certificate by executing the following command: Windows: - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
Re: Tomcat 6.0.33 ?
On 27/07/2011 17:31, Henri Gomez wrote: > Hi guys, > > We're stuck with Tomcat 6.0.32 with this bug > (https://issues.apache.org/bugzilla/show_bug.cgi?id=50189). > Did there is any date for 6.0.33 release ? Any committer can roll a release. Last time I checked, you were a committer. If you don't have time to roll the release but want to help it along, you could review and vote on some of outstanding patches in the status file. Mark - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
DO NOT REPLY [Bug 48997] enhance ssl-howto documentation
https://issues.apache.org/bugzilla/show_bug.cgi?id=48997 --- Comment #4 from Mark Thomas 2011-07-27 17:09:27 UTC --- Similar changes made in 6.0.x and will be in 6.0.33 onwards. -- Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
svn commit: r1151536 - in /tomcat/tc6.0.x/trunk/webapps/docs: changelog.xml ssl-howto.xml
Author: markt
Date: Wed Jul 27 17:09:30 2011
New Revision: 1151536
URL: http://svn.apache.org/viewvc?rev=1151536&view=rev
Log:
https://issues.apache.org/bugzilla/show_bug.cgi?id=48997
Fixed some typos and improve cross-referencing to the HTTP Connector and APR
documentation with the SSL How-To page of the documentation web application.
Modified:
tomcat/tc6.0.x/trunk/webapps/docs/changelog.xml
tomcat/tc6.0.x/trunk/webapps/docs/ssl-howto.xml
Modified: tomcat/tc6.0.x/trunk/webapps/docs/changelog.xml
URL:
http://svn.apache.org/viewvc/tomcat/tc6.0.x/trunk/webapps/docs/changelog.xml?rev=1151536&r1=1151535&r2=1151536&view=diff
==
--- tomcat/tc6.0.x/trunk/webapps/docs/changelog.xml (original)
+++ tomcat/tc6.0.x/trunk/webapps/docs/changelog.xml Wed Jul 27 17:09:30 2011
@@ -278,6 +278,11 @@
configuration page in the documentation web application. (markt)
+48997: Fixed some typos and improve cross-referencing to the
+HTTP Connector and APR documentation with the SSL How-To page of the
+documentation web application. (markt)
+
+
50804: Update links for Servlet 2.5 and JSP 2.1 Javadoc.
(markt)
Modified: tomcat/tc6.0.x/trunk/webapps/docs/ssl-howto.xml
URL:
http://svn.apache.org/viewvc/tomcat/tc6.0.x/trunk/webapps/docs/ssl-howto.xml?rev=1151536&r1=1151535&r2=1151536&view=diff
==
--- tomcat/tc6.0.x/trunk/webapps/docs/ssl-howto.xml (original)
+++ tomcat/tc6.0.x/trunk/webapps/docs/ssl-howto.xml Wed Jul 27 17:09:30 2011
@@ -47,7 +47,8 @@
To install and configure SSL support on Tomcat 6, you need to follow
these simple steps. For more information, read the rest of this HOW-TO.
-Create a certificate keystore by executing the following command:
+Create a keystore file to store the server's private key and
+self-signed certificate by executing the following command:
Windows:
%JAVA_HOME%\bin\keytool -genkey -alias tomcat -keyalg RSA
@@ -375,13 +376,16 @@ file installed with Tomcat. For JSSE, i
-You will note that the Connector element itself is commented out by default,
-so you will need to remove the comment tags around it. Then, you can
-customize the specified attributes as necessary. For detailed information
-about the various options, consult the
-Server Configuration Reference. The
-following discussion covers only those attributes of most interest when
-setting up SSL communication.
+You will note that the example SSL connector elements are commented out by
+default. You can either remove the comment tags from around the the example SSL
+connector you wish to use or add a new Connector element of your own. In either
+case, you will need to configure the SSL Connector for your requirements
+and environment. The configuration options and information on which attributes
+are mandatory for the JSSE based connectors (BIO and NIO) are documented in the
+SSL Support section of the HTTP
+connector configuration reference. The configuration options and
information
+on which attributes are mandatory for the APR connector are documented in the
+HTTPS section of the APR How-To.
The port attribute (default value is 8443) is the TCP/IP
port number on which Tomcat will listen for secure connections. You can
@@ -398,15 +402,6 @@ numbers lower than 1024 on many operatin
that SSL is required, as required by the Servlet Specification.
-There are additional options used to configure the SSL protocol. You may
-need to add or change some attributes, depending on how you configured your
-keystore earlier. If you are using a Java JSSE based SSL connector then
-configuration options are documented in the
-Java HTTP connector configuration
-reference. If you are using the APR/native connector then refer to the
-APR connector configuration guide for details of the
-available configuration options.
-
After completing these configuration changes, you must restart Tomcat as
you normally do, and you should be in business. You should be able to access
any web application supported by Tomcat via SSL. For example, try:
@@ -482,13 +477,6 @@ SSL communications, and what to do about
-I get "java.security.NoSuchAlgorithmException" errors in my
-log files.
-
-The JVM cannot find the JSSE JAR files. Follow all of the directions to
-download and install JSSE.
-
-
When Tomcat starts up, I get an exception like
"java.io.FileNotFoundException: {some-directory}/{some-file} not found".
@@ -523,7 +511,7 @@ SSL communications, and what to do about
enabled."
A likely explanation is that Tomcat cannot find the alias for the server
-key withinthe specified keystore. Check that the correct
+key within the specified keystore. Check that the correct
keystoreFile and keyAlias are specified in the
element i
svn commit: r1151537 - in /tomcat/tc5.5.x/trunk/container/webapps/docs: changelog.xml ssl-howto.xml
Author: markt Date: Wed Jul 27 17:14:06 2011 New Revision: 1151537 URL: http://svn.apache.org/viewvc?rev=1151537&view=rev Log: CTR: Docs https://issues.apache.org/bugzilla/show_bug.cgi?id=48997 Fixed some typos and improve cross-referencing to the HTTP Connector and APR documentation with the SSL How-To page of the documentation web application. Modified: tomcat/tc5.5.x/trunk/container/webapps/docs/changelog.xml tomcat/tc5.5.x/trunk/container/webapps/docs/ssl-howto.xml Modified: tomcat/tc5.5.x/trunk/container/webapps/docs/changelog.xml URL: http://svn.apache.org/viewvc/tomcat/tc5.5.x/trunk/container/webapps/docs/changelog.xml?rev=1151537&r1=1151536&r2=1151537&view=diff == --- tomcat/tc5.5.x/trunk/container/webapps/docs/changelog.xml (original) +++ tomcat/tc5.5.x/trunk/container/webapps/docs/changelog.xml Wed Jul 27 17:14:06 2011 @@ -72,6 +72,11 @@ conf/catalina.policy file when the documentation is built, rather than maintaining a copy of its content. (kkolinko) + +48997: Fixed some typos and improve cross-referencing to the +HTTP Connector and APR documentation with the SSL How-To page of the +documentation web application. (markt) + Modified: tomcat/tc5.5.x/trunk/container/webapps/docs/ssl-howto.xml URL: http://svn.apache.org/viewvc/tomcat/tc5.5.x/trunk/container/webapps/docs/ssl-howto.xml?rev=1151537&r1=1151536&r2=1151537&view=diff == --- tomcat/tc5.5.x/trunk/container/webapps/docs/ssl-howto.xml (original) +++ tomcat/tc5.5.x/trunk/container/webapps/docs/ssl-howto.xml Wed Jul 27 17:14:06 2011 @@ -52,7 +52,8 @@ To install and configure SSL support on Tomcat 5, you need to follow these simple steps. For more information, read the rest of this HOW-TO. -Create a certificate keystore by executing the following command: +Create a keystore file to store the server's private key and +self-signed certificate by executing the following command: Windows: %JAVA_HOME%\bin\keytool -genkey -alias tomcat -keyalg RSA @@ -372,13 +373,17 @@ file installed with Tomcat. For JSSE, i -You will note that the Connector element itself is commented out by default, -so you will need to remove the comment tags around it. Then, you can -customize the specified attributes as necessary. For detailed information -about the various options, consult the -Server Configuration Reference. The -following discussion covers only those attributes of most interest when -setting up SSL communication. +You will note that the example SSL connector elements are commented out by +default. You can either remove the comment tags from around the the example SSL +connector you wish to use or add a new Connector element of your own. In either +case, you will need to configure the SSL Connector for your requirements +and environment. The configuration options and information on which attributes +are mandatory for the JSSE based connector (BIO) are documented in the +SSL Support section of the HTTP +connector configuration reference. The configuration options and information +on which attributes are mandatory for the APR connector are documented in the +HTTPS section of the APR How-To. + The port attribute (default value is 8443) is the TCP/IP port number on which Tomcat will listen for secure connections. You can @@ -395,15 +400,6 @@ numbers lower than 1024 on many operatin that SSL is required, as required by the Servlet Specification. -There are additional options used to configure the SSL protocol. You may -need to add or change some attributes, depending on how you configured your -keystore earlier. If you are using a Java JSSE based SSL connector then -configuration options are documented in the -Java HTTP connector configuration -reference. If you are using the APR/native connector then refer to the -APR connector configuration guide for details of the -available configuration options. - After completing these configuration changes, you must restart Tomcat as you normally do, and you should be in business. You should be able to access any web application supported by Tomcat via SSL. For example, try: @@ -520,7 +516,7 @@ SSL communications, and what to do about enabled." A likely explanation is that Tomcat cannot find the alias for the server -key withinthe specified keystore. Check that the correct +key within the specified keystore. Check that the correct keystoreFile and keyAlias are specified in theelement in the Tomcat configuration file. - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
DO NOT REPLY [Bug 48997] enhance ssl-howto documentation
https://issues.apache.org/bugzilla/show_bug.cgi?id=48997 Mark Thomas changed: What|Removed |Added Status|NEW |RESOLVED Resolution||FIXED --- Comment #5 from Mark Thomas 2011-07-27 17:14:20 UTC --- And finally fixed in 5.5.x for 5.5.34 onwards. -- Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
Re: Servlet 3.1, Tomcat 8 etc.
On 07/27/2011 06:53 PM, Mark Thomas wrote: On 27/07/2011 16:48, Mladen Turk wrote: After we release first 8 stable or starting from now? I was thinking announce EOL for 5.5.x now, with the actual EOL date / last release ~August 2012. OK, but IMHO we should add +12 months to that for critical security issues. I mean no bug fixes, only CVE's Possible? Regards -- ^TM - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
Re: Servlet 3.1, Tomcat 8 etc.
On 27/07/2011 18:26, Mladen Turk wrote: > On 07/27/2011 06:53 PM, Mark Thomas wrote: >> On 27/07/2011 16:48, Mladen Turk wrote: >>> >>> After we release first 8 stable or starting from now? >> >> I was thinking announce EOL for 5.5.x now, with the actual EOL date / >> last release ~August 2012. >> > > OK, but IMHO we should add +12 months to that for critical security > issues. I mean no bug fixes, only CVE's > > Possible? Anything is possible. We didn't do that for 4.1.x but if you want to do that for 5.5.x then there is nothing stopping you. Mark - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
DO NOT REPLY [Bug 51567] New: Classloader docs don't address CATALINA_BASE
https://issues.apache.org/bugzilla/show_bug.cgi?id=51567 Bug #: 51567 Summary: Classloader docs don't address CATALINA_BASE Product: Tomcat 7 Version: unspecified Platform: PC Status: NEW Severity: normal Priority: P2 Component: Documentation AssignedTo: dev@tomcat.apache.org ReportedBy: jonwilm...@yahoo.com Classification: Unclassified The http://tomcat.apache.org/tomcat-7.0-doc/class-loader-howto.html docs do a great job of defining the priority of classloaders for a deployment where CATALINA_HOME is the same as CATALINA_BASE. Through some experimentation it appears CATALINA_BASE/lib is also searched for classes. It would be nice to see the docs reflect the additional location(s) searched and the order in which they are. For example will CATALINA_BASE/lib/some-classes.jar take precedence over CATALINA_HOME/lib/some-classes.jar? -- Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
Re: Tomcat 6.0.33 ?
> Any committer can roll a release. Last time I checked, you were a committer. Any commiter can roll a release but if there is a consensus isn't it ? I guess no-one here decide by itself to roll a release ? > If you don't have time to roll the release but want to help it along, > you could review and vote on some of outstanding patches in the status file. I do release in the past for mod_jk but never for Tomcat 6 so I could works on this but not alone, I don't want to do mistakes - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
Re: [VOTE] Release Apache Tomcat Native 1.1.21
On 07/27/2011 02:04 PM, Mladen Turk wrote: On 07/27/2011 11:20 AM, jean-frederic clere wrote: Win32/Win64 binaries will be available at: http://tomcat.apache.org/dev/dist/tomcat-connectors/native/1.1.21/binaries/ Think we should stop shipping anything that is not voted for. You should have call for a vote after the binaries are uploaded. Otherwise we would need a new vote for the binaries. Well does it make sense to vote for a binary? Cheers Jean-Frederic - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
Re: Tomcat 6.0.33 ?
On 07/27/2011 07:07 PM, Mark Thomas wrote: On 27/07/2011 17:31, Henri Gomez wrote: Hi guys, We're stuck with Tomcat 6.0.32 with this bug (https://issues.apache.org/bugzilla/show_bug.cgi?id=50189). Did there is any date for 6.0.33 release ? Any committer can roll a release. Last time I checked, you were a committer. Well I can do a release... Next week. Cheers Jean-Frederic - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
Re: Tomcat 6.0.33 ?
> Well I can do a release... Next week. Many thanks Jean-Fred. I'll happy to help for a next release but need more informations on the full process. - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
Re: Servlet 3.1, Tomcat 8 etc.
On 07/27/2011 06:53 PM, Mark Thomas wrote: On 27/07/2011 16:48, Mladen Turk wrote: On 07/26/2011 07:30 PM, Mark Thomas wrote: 1. Should tomcat/tc7.0.x/trunk be RTC or CTR? CTR 2. With tomcat/trunk becoming the basis for Tomcat 8, I would like to see earlier and more frequent alpha/beta releases than we had for Tomcat Sure. This time we might have 8 ready as 3.1 spec is defined. I have no problem if it's bound to spec RC cause it won't be stable until 3.1 spec is frozen. 7. That would increase the effective number of versions we are supporting. With that in mind, should we announce end of support for 5.5.x with the last release expected in ~12 months time? After we release first 8 stable or starting from now? I was thinking announce EOL for 5.5.x now, with the actual EOL date / last release ~August 2012. +1 Cheers Jean-Frederic - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
