[ANN] Apache Tomcat 11.0.0-M9 (alpha) available

[Mark Thomas]

The Apache Tomcat team announces the immediate availability of Apache
Tomcat 11.0.0-M9 (alpha).

Apache Tomcat 11 is an open source software implementation of the
Jakarta Servlet, Jakarta Server Pages, Jakarta Expression Language,
Jakarta WebSocket, Jakarta Authentication and Jakarta Annotations
specifications.

Users of Tomcat 10 onwards should be aware that, as a result of the move
from Java EE to Jakarta EE as part of the transfer of Java EE to the
Eclipse Foundation, the primary package for all implemented APIs has
changed from javax.* to jakarta.*. This will almost certainly require
code changes to enable applications to migrate from Tomcat 9 and earlier
to Tomcat 10 and later. A migration tool is available to aid this process.

Apache Tomcat 11.0.0-M9 is a milestone release of the 11.0.x branch and 
has been made to provide users with early access to the new features in 
Apache Tomcat 11.0.x so that they may provide feedback. The notable 
changes compared to 11.0.0-M7 include:


- Add ContextNamingInfoListener, a listener which creates context naming
  information environment entries

- Add PropertiesRoleMappingListener, a listener which populates the
  context's role mapping from a properties file.

- Update the Jakarta EL and Jakarta WebSocket implementations to align
  with the latest changes planned for Jakarta EE 11

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

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

Migration guides from Apache Tomcat 8.5.x, 9.0.x and 10.1.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

[tomcat] branch main updated (5a7bb27da6 -> 52ed442408)

[markt]

This is an automated email from the ASF dual-hosted git repository.

markt pushed a change to branch main
in repository https://gitbox.apache.org/repos/asf/tomcat.git


from 5a7bb27da6 Fix string ms -> s
 add 52ed442408 Add release date for 11.0.0-M9

No new revisions were added by this update.

Summary of changes:
 webapps/docs/changelog.xml | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)


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

[Bug 66684] SSL HandShake failed when crlFile linked to an empty file

[bugzilla]

https://bz.apache.org/bugzilla/show_bug.cgi?id=66684

Michael Osipov  changed:

   What|Removed |Added

 OS||All

--- Comment #1 from Michael Osipov  ---
(In reply to DigitalCat from comment #0)
> Recently, we tested the use of the crLFile configuration （in server.xml） in
> the scenario where two-way certificate authentication is enabled. When the
> file pointed to by the crlFile configuration item is an empty file (the file
> exists but the file content is blank), Tomcat cannot provide services and
> SSL HandShake reports an error（certificate_unknown）. When crlFile is not
> configured or the content in crlFile is correct, no error is reported.
> 
> I'm thinking that don't need to set the revocationEnabled parameter to true
> (In org.apache.tomcat.util.net.SSLUtilBase#getParameters 498L) when the file
> content is blank.

If you set a path and the file exists, Tomcat will use as-is. What do you
expect?

-- 
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

[Bug 66684] SSL HandShake failed when crlFile linked to an empty file

[bugzilla]

https://bz.apache.org/bugzilla/show_bug.cgi?id=66684

--- Comment #2 from DigitalCat  ---
Here is my PR：https://github.com/apache/tomcat/pull/634

I expect that the Tomcat can provide services normally when the crlFile file is
a blank file. Generally, the crlFile file may be a blank file at the beginning
because the CA has not delivered the crl file with content.

-- 
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

Buildbot failure in on tomcat-11.0.x

[buildbot]

Build status: BUILD FAILED: failed compile (failure)
Worker used: bb_worker2_ubuntu
URL: https://ci2.apache.org/#builders/112/builds/479
Blamelist: Mark Thomas 
Build Text: failed compile (failure)
Status Detected: new failure
Build Source Stamp: [branch main] 52ed44240892c96c336ac48275427547980366c9


Steps:

  worker_preparation: 0

  git: 0

  shell: 0

  shell_1: 0

  shell_2: 0

  shell_3: 0

  shell_4: 0

  shell_5: 0

  compile: 1

  shell_6: 0

  shell_7: 0

  shell_8: 0

  shell_9: 0

  Rsync docs to nightlies.apache.org: 0

  shell_10: 0

  Rsync RAT to nightlies.apache.org: 0

  compile_1: 2

  shell_11: 0

  Rsync Logs to nightlies.apache.org: 0


-- ASF Buildbot


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

[Bug 66685] New: Tomcat URL not picking correct certificate

[bugzilla]

https://bz.apache.org/bugzilla/show_bug.cgi?id=66685

Bug ID: 66685
   Summary: Tomcat URL not picking correct certificate
   Product: Tomcat 8
   Version: 8.5.32
  Hardware: PC
Status: NEW
  Severity: major
  Priority: P2
 Component: Catalina
  Assignee: dev@tomcat.apache.org
  Reporter: bhushan.pad...@gmail.com
  Target Milestone: 

Hello Team,

We have configured HTTPS, generated the keystore usign keytool command
generated the CSR then signed it and imported in the keystore  and updated the
server.xml file with the keystore path and password and restarted the tomcat
service but it is still taking the old certificate and we are getting the https
warning.

Could you please suggest how to make sure that the url will take the correct
certificate while.

from where or the path the tomcat/url picks the certificate.

Thanks
Bhushan Padala

-- 
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

[Bug 66684] SSL HandShake failed when crlFile linked to an empty file

[bugzilla]

https://bz.apache.org/bugzilla/show_bug.cgi?id=66684

--- Comment #3 from Remy Maucherat  ---
The "empty file then do nothing" behavior sounds the most intuitive to me.
Although obviously this was not handheld because it's not really expected when
initially writing the code.

-- 
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

[Bug 66684] SSL HandShake failed when crlFile linked to an empty file

[bugzilla]

https://bz.apache.org/bugzilla/show_bug.cgi?id=66684

--- Comment #4 from Michael Osipov  ---
(In reply to DigitalCat from comment #2)
> Here is my PR：https://github.com/apache/tomcat/pull/634
> 
> I expect that the Tomcat can provide services normally when the crlFile file
> is a blank file. Generally, the crlFile file may be a blank file at the
> beginning because the CA has not delivered the crl file with content.

I think this would apply to many cert-related files? Check for blanks.

-- 
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

[Bug 66686] New: Default value of maxParameterCount

[bugzilla]

https://bz.apache.org/bugzilla/show_bug.cgi?id=66686

Bug ID: 66686
   Summary: Default value of maxParameterCount
   Product: Tomcat 9
   Version: 9.0.78
  Hardware: PC
OS: Linux
Status: NEW
  Severity: trivial
  Priority: P2
 Component: Documentation
  Assignee: dev@tomcat.apache.org
  Reporter: michal.sobkiew...@wp.pl
  Target Milestone: -

Documentation (https://tomcat.apache.org/tomcat-9.0-doc/config/http.html) says,
that the default value for maxParameterCount is 1000, when in fact, for Tomcat
9.x, it is still 1.

See
https://github.com/apache/tomcat/blob/9.0.78/java/org/apache/catalina/connector/Connector.java#L197-L201
to confirm.

-- 
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

[Bug 66686] Default value of maxParameterCount

[bugzilla]

https://bz.apache.org/bugzilla/show_bug.cgi?id=66686

Remy Maucherat  changed:

   What|Removed |Added

 Resolution|--- |WONTFIX
 Status|NEW |RESOLVED

--- Comment #1 from Remy Maucherat  ---
The actual new default is in the default server.xml (maxParameterCount="1000"),
while the other one is unchanged (in that branch) for full compatibility.

-- 
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

[Bug 66686] Default value of maxParameterCount

[bugzilla]

https://bz.apache.org/bugzilla/show_bug.cgi?id=66686

--- Comment #2 from michal.sobkiew...@wp.pl ---
That's true. However when _unspecified_, the default is 1. Documentation is
misleading.

-- 
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

multipart streaming as fileupload native usage?

[Romain Manni-Bucau]

Hi all,

on commons fileupload list there was the need to have streaming for Parts.

As of today Servlet API enables to only get a list and not an iterator -
even if it uses it under the hood.
Any way tomcat pushes that need (Iterator or Stream I guess) to the servlet
EG for next version?
Do we want to provide this thru the current API implementing a LazyList
(while only Iterator is touched the list is not materialized)?

Romain Manni-Bucau
@rmannibucau  |  Blog
 | Old Blog
 | Github  |
LinkedIn  | Book

[Bug 66686] Default value of maxParameterCount

[bugzilla]

https://bz.apache.org/bugzilla/show_bug.cgi?id=66686

msobkiewicz  changed:

   What|Removed |Added

 Resolution|WONTFIX |---
 Status|RESOLVED|REOPENED

--- Comment #3 from msobkiewicz  ---
Documentation says:
"If not specified, a default of 1000 is used."

Documentation should say:
"If not specified, a default of 1 is used."

-- 
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