Re: Requesting the confirmation

[Koteswararao Gundapaneni]

Requesting you as I work for solve the bug


Re
Koti



On Sat, 27 Jul 2024, 14:40 Mark Thomas,  wrote:

> Request denied.
>
> You have yet to make any meaningful contribution to the Tomcat community.
>
> You are remain very, very close to receiving a permanent ban from the
> Tomcat community as a result of multiple nonsense posts.
>
> Mark
>
>
> On 27/07/2024 04:21, Koteswararao Gundapaneni wrote:
> > Hi Team,
> >
> >
> > I got placed to Verizon so I could requesting you to say that I have been
> > working as a contributor
> >
> > That will help me to work further
> >
> >
> > Warm Regards
> > Koti
> >
>

Requesting the confirmation

[Koteswararao Gundapaneni]

Hi Team,


I got placed to Verizon so I could requesting you to say that I have been
working as a contributor

That will help me to work further


Warm Regards
Koti

Re: Simplifying JreCompat

[Koteswararao Gundapaneni]

I am not sure whether this question is relevant


What is this JreCompat

On Fri, 26 Jul 2024, 02:04 Mark Thomas,  wrote:

> As per Rémy's suggestion, I've been looking simplifying JreCompat to
> only support LTS versions and anything more recent than the newest LTS.
>
> That would mean:
> - Tomcat 9 only
>- Jre9Compat is renamed to Jre11Compat
> - Tomcat 9 and 10
>- Jre16Compat is renamed to Jre17Compat
> - All versions
>- Jre18Compat and Jre19Compat are merged into the existing Jre21Compat
>
> Jre22Compat would be unchanged.
>
> So the only real change is merging Jre18Compat, Jre19Compat and
> Jre21Compat into a single, larger Jre21Compat.
>
> I'm on the fence as to whether this is worth doing. Thoughts?
>
> Mark
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
> For additional commands, e-mail: dev-h...@tomcat.apache.org
>
>

Re: (tomcat) 03/09: Refactor writing of the status code

[Koteswararao Gundapaneni]

Hi Mark,

response.getStatus() should be identical I mean it is json eval


On Fri, 19 Jul 2024, 20:39 ,  wrote:

> This is an automated email from the ASF dual-hosted git repository.
>
> markt pushed a commit to branch main
> in repository https://gitbox.apache.org/repos/asf/tomcat.git
>
> commit ff7a869fd203b3b60ffd699c47da1d07e77f0c3a
> Author: Mark Thomas 
> AuthorDate: Thu Jul 4 14:15:50 2024 +0100
>
> Refactor writing of the status code
>
> This refactoring is part of the preparation for RFC 8297 (Early Hints)
> support.
> ---
>  java/org/apache/coyote/http11/Http11OutputBuffer.java | 14 +-
>  java/org/apache/coyote/http11/Http11Processor.java|  4 ++--
>  2 files changed, 15 insertions(+), 3 deletions(-)
>
> diff --git a/java/org/apache/coyote/http11/Http11OutputBuffer.java
> b/java/org/apache/coyote/http11/Http11OutputBuffer.java
> index be7955c1b0..76fdb0d126 100644
> --- a/java/org/apache/coyote/http11/Http11OutputBuffer.java
> +++ b/java/org/apache/coyote/http11/Http11OutputBuffer.java
> @@ -320,14 +320,26 @@ public class Http11OutputBuffer implements
> HttpOutputBuffer {
>
>  /**
>   * Send the response status line.
> + *
> + * @deprecated Unused. Will be removed in Tomcat 11. Use {@link
> #sendStatus(int)}.
>   */
> +@Deprecated
>  public void sendStatus() {
> +sendStatus(response.getStatus());
> +}
> +
> +
> +/**
> + * Send the response status line.
> + *
> + * @param status The HTTP status code to include in the status line
> + */
> +public void sendStatus(int status) {
>  // Write protocol name
>  write(Constants.HTTP_11_BYTES);
>  headerBuffer.put(Constants.SP);
>
>  // Write status code
> -int status = response.getStatus();
>  switch (status) {
>  case 200:
>  write(Constants._200_BYTES);
> diff --git a/java/org/apache/coyote/http11/Http11Processor.java
> b/java/org/apache/coyote/http11/Http11Processor.java
> index 681db0e96b..f6f34e8f45 100644
> --- a/java/org/apache/coyote/http11/Http11Processor.java
> +++ b/java/org/apache/coyote/http11/Http11Processor.java
> @@ -1037,7 +1037,7 @@ public class Http11Processor extends
> AbstractProcessor {
>
>  // Build the response header
>  try {
> -outputBuffer.sendStatus();
> +outputBuffer.sendStatus(response.getStatus());
>
>  int size = headers.size();
>  for (int i = 0; i < size; i++) {
> @@ -1054,7 +1054,7 @@ public class Http11Processor extends
> AbstractProcessor {
>  outputBuffer.resetHeaderBuffer();
>  // -1 as it will be incremented at the start of the
> loop and header indexes start at 0.
>  i = -1;
> -outputBuffer.sendStatus();
> +outputBuffer.sendStatus(response.getStatus());
>  }
>  }
>  outputBuffer.endHeaders();
>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
> For additional commands, e-mail: dev-h...@tomcat.apache.org
>
>

Re: (tomcat) 06/07: Add HTTP/2 support for early hints

[Koteswararao Gundapaneni]

Hi Mark,


OpenclientConnection should be ftp rather than tcpip

Re
Koti




On Fri, 19 Jul 2024, 21:56 ,  wrote:

> This is an automated email from the ASF dual-hosted git repository.
>
> markt pushed a commit to branch 10.1.x
> in repository https://gitbox.apache.org/repos/asf/tomcat.git
>
> commit ae22fadba4b94152fa5cc1d015ed2058f21e3164
> Author: Mark Thomas 
> AuthorDate: Thu Jul 4 16:53:21 2024 +0100
>
> Add HTTP/2 support for early hints
> ---
>  java/org/apache/coyote/http2/Stream.java   | 16 ++
>  java/org/apache/coyote/http2/StreamProcessor.java  |  3 +-
>  .../apache/coyote/http2/TestStreamProcessor.java   | 66
> ++
>  3 files changed, 83 insertions(+), 2 deletions(-)
>
> diff --git a/java/org/apache/coyote/http2/Stream.java
> b/java/org/apache/coyote/http2/Stream.java
> index a72bba3a7b..3e621e82a8 100644
> --- a/java/org/apache/coyote/http2/Stream.java
> +++ b/java/org/apache/coyote/http2/Stream.java
> @@ -597,6 +597,22 @@ class Stream extends AbstractNonZeroStream implements
> HeaderEmitter {
>  }
>
>
> +final void writeEarlyHints() throws IOException {
> +MimeHeaders headers = coyoteResponse.getMimeHeaders();
> +String originalStatus = headers.getHeader(":status");
> +headers.setValue(":status").setString("103");
> +try {
> +handler.writeHeaders(this, 0, headers, false,
> Constants.DEFAULT_HEADERS_FRAME_SIZE);
> +} finally {
> +if (originalStatus == null) {
> +headers.removeHeader(":status");
> +} else {
> +headers.setValue(":status").setString(originalStatus);
> +}
> +}
> +}
> +
> +
>  @Override
>  final String getConnectionId() {
>  return handler.getConnectionId();
> diff --git a/java/org/apache/coyote/http2/StreamProcessor.java
> b/java/org/apache/coyote/http2/StreamProcessor.java
> index 3f3cde6f50..b7d6e9e6ce 100644
> --- a/java/org/apache/coyote/http2/StreamProcessor.java
> +++ b/java/org/apache/coyote/http2/StreamProcessor.java
> @@ -263,8 +263,7 @@ class StreamProcessor extends AbstractProcessor {
>
>  @Override
>  protected void earlyHints() throws IOException {
> -// TODO Auto-generated method stub
> -// NO-OP for now
> +stream.writeEarlyHints();
>  }
>
>
> diff --git a/test/org/apache/coyote/http2/TestStreamProcessor.java
> b/test/org/apache/coyote/http2/TestStreamProcessor.java
> index ac362c6e30..5082349a6e 100644
> --- a/test/org/apache/coyote/http2/TestStreamProcessor.java
> +++ b/test/org/apache/coyote/http2/TestStreamProcessor.java
> @@ -36,6 +36,7 @@ import org.junit.Test;
>  import org.apache.catalina.Context;
>  import org.apache.catalina.Wrapper;
>  import org.apache.catalina.connector.Connector;
> +import org.apache.catalina.connector.ResponseFacade;
>  import org.apache.catalina.startup.Tomcat;
>  import org.apache.tomcat.util.compat.JrePlatform;
>  import org.apache.tomcat.util.http.FastHttpDateFormat;
> @@ -586,4 +587,69 @@ public class TestStreamProcessor extends
> Http2TestBase {
>  String trace = output.getTrace();
>  Assert.assertTrue(trace,
> trace.contains("3-Header-[:status]-[501]"));
>  }
> +
> +
> +@Test
> +public void testEarlyHints() throws Exception {
> +enableHttp2();
> +
> +Tomcat tomcat = getTomcatInstance();
> +
> +Context ctxt = getProgrammaticRootContext();
> +Tomcat.addServlet(ctxt, "simple", new SimpleServlet());
> +ctxt.addServletMappingDecoded("/simple", "simple");
> +Tomcat.addServlet(ctxt, "ehs", new EarlyHintsServlet());
> +ctxt.addServletMappingDecoded("/ehs", "ehs");
> +tomcat.start();
> +
> +openClientConnection();
> +doHttpUpgrade();
> +sendClientPreface();
> +validateHttp2InitialResponse();
> +
> +// Disable overhead protection for window update as it breaks
> some tests
> +http2Protocol.setOverheadWindowUpdateThreshold(0);
> +
> +byte[] headersFrameHeader = new byte[9];
> +ByteBuffer headersPayload = ByteBuffer.allocate(128);
> +
> +buildGetRequest(headersFrameHeader, headersPayload, null, 3,
> "/ehs");
> +
> +// Write the headers
> +writeFrame(headersFrameHeader, headersPayload);
> +
> +parser.readFrame();
> +
> +Assert.assertEquals("3-HeadersStart\n" +
> "3-Header-[:status]-[103]\n" +
> +"3-Header-[link]-[; rel=preload; as=style]\n"
> + "3-HeadersEnd\n", output.getTrace());
> +output.clearTrace();
> +
> +parser.readFrame();
> +parser.readFrame();
> +
> +Assert.assertEquals("3-HeadersStart\n" +
> "3-Header-[:status]-[200]\n" +
> +"3-Header-[link]-[; rel=preload; as=style]\n"
> +
> +"3-Header-[content-type]-[text/plain;charset=UTF-8]\n" +
> +"3-Header-[content-length]-[2]\n" +
> +"3-Header-[date]-[" + DEFAULT_

Re: Security mechanisms to counter spam

[Koteswararao Gundapaneni]

Hi Dimitris,

We could potentially block but it is as per the agreement

On Fri, 7 Jun 2024, 15:53 Dimitris Soumis,  wrote:

> Hi All,
>
> Due to the surge in spam BZs today, I propose implementing a security
> mechanism to counter this issue and prevent further disruption to the
> mailing list.
>
> A potential solution could include a honeypot to identify and block bots,
> as well as a reCaptcha to verify users. Additionally, should monitor for
> multiple requests from the same IP address and block the IP if necessary.
>
> Can also leverage tools like this Mozilla Bugbot Spam Detection Script
>  to
> identify and filter out spam.
>
> Best regards,
>
> Dimitris
>

Re: Short and long term plans for Tomcat Native

[Koteswararao Gundapaneni]

Hi Mark


Do we need the app is maintained or to be noticed

On Wed, 17 Jul 2024, 21:04 Mark Thomas,  wrote:

> All,
>
> I've spent some time today trying to build Tomcat Native with Visual
> Studio 2022 rather then the current, more involved process without success.
>
> Therefore, my short-term plan for Tomcat Native is to get the next 2.0.x
> and 1.3.x releases completed using the existing build process. I'll be
> starting that shortly.
>
> Longer term, thinking about Tomcat Native and FFM I have the following
> rough plan in mind:
>
> - stop providing x86 binaries for Windows
> - require Windows 10 onwards
> - provide:
>- libssl.dll
>- libcrypto.dll
>- tomcat-native-2.dll
>- openssl.exe
>
> along with appropriate debug symbols.
>
> I'm not sure if we'd need an apr.dll in there as well.
>
> The idea is that users can then use either the AprLifecycleListener or
> OpenSSLLifecycleListener.
>
> This would probably require moving Tomcat Native to 2.1.x and 1.4.x
>
> This really needs someone more familiar with building C libraries
> generally and these libraries in particular - i.e. Mladen - to say
> whether the above is possible and to provide some pointers on how to do it.
>
> Mark
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
> For additional commands, e-mail: dev-h...@tomcat.apache.org
>
>

Re: APPROVE MY ICLA

[Koteswararao Gundapaneni]

Thanx for sharing the policy document with me

On Mon, 15 Apr 2024, 09:21 Han Li,  wrote:

> Please read this document[1] carefully, how to become a committer.
>
> Again, there is no thread about inviting you to become a committer, so you
> don't have to sign ICLA, so please don't spam us like this again.
>
> Han
>
> [1] https://community.apache.org/newcommitter.html#new-committer-process
>
> > On Apr 15, 2024, at 10:05, Koteswararao Gundapaneni <
> apache.tomcat.k...@gmail.com> wrote:
> >
> > Please approve my request
> >
> > -
> > To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
> > For additional commands, e-mail: dev-h...@tomcat.apache.org
>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
> For additional commands, e-mail: dev-h...@tomcat.apache.org
>
>

Re: APPROVE MY ICLA

[Koteswararao Gundapaneni]

On Mon, 15 Apr 2024, 07:35 Koteswararao Gundapaneni, <
apache.tomcat.k...@gmail.com> wrote:

> Please approve my request
>

APPROVE MY ICLA

[Koteswararao Gundapaneni]

Please approve my request

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

Re: HTTP / 3 protocol updates

[Koteswararao Gundapaneni]

Looks like understanding the quick protocol quiet cumbersome


Anyway preparing the design document




On Tue, 26 Mar 2024, 15:38 Koteswararao Gundapaneni, <
apache.tomcat.k...@gmail.com> wrote:

>
>
> Let me come up with design document
>
>
> Regards
> Koti
>
> On Mon, 25 Mar 2024, 19:02 Christopher Schultz, <
> ch...@christopherschultz.net> wrote:
>
>> Koti,
>>
>> On 3/24/24 11:30, Koteswararao Gundapaneni wrote:
>> > When can I expect the update on the HTTP/3 protocol implementation?
>> >
>> >
>> > HTTP/3
>> >
>> > RFC 9114 <https://datatracker.ietf.org/doc/html/rfc9114> (June 2022) -
>> > HTTP/3
>> >
>> > Not yet implemented by Apache Tomcat. (As of July 2022)
>>
>> Why pick "July 2022" as an arbitrary date to be not-implemented-as-of
>> instead of, say, TODAY?
>>
>> > https://datatracker.ietf.org/doc/html/rfc9114#section-1.1-2
>>
>> (This reference doesn't seem relevant.)
>>
>> h3 is not currently a priority for the Apache Tomcat team, for several
>> reasons:
>>
>> 1. Tomcat is very often used behind a reverse proxy, where persistent
>> HTTP or h2 connections can be used to "solve" the
>> connection-establishment "problem".
>>
>> 2. Java does not currently provide an implementation of h3. This means
>> we either have to wait for Java to provide such an implementation or
>> look to outside libraries such as Quiche. One of the goals of Tomcat is
>> to have as few dependencies as possible, so using Quiche, etc. would be
>> contrary to those goals.
>>
>> 3. OpenSSL currently does provide an implementation of h3 but it is very
>> different than both the current implementation of TLS and also anything
>> offered by Java (which does not yet exist).
>>
>> This is a project run by a small group of volunteers, not a large
>> company with many resources. We all have "day jobs" where we spend most
>> of our time.
>>
>> You've been making inquiries about becoming a committer on the project.
>> One way to score a lot of points towards that might be to propose a
>> working implementation of h3 that can be added to a currently-supported
>> version of Tomcat. I would encourage you to work exclusively on the 11.x
>> branch, as that is where most new functionality is added before being
>> back-ported to the other stable branches.
>>
>> -chris
>>
>> -
>> To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
>> For additional commands, e-mail: dev-h...@tomcat.apache.org
>>
>>

Re: HTTP / 3 protocol updates

[Koteswararao Gundapaneni]

Let me come up with design document


Regards
Koti

On Mon, 25 Mar 2024, 19:02 Christopher Schultz, <
ch...@christopherschultz.net> wrote:

> Koti,
>
> On 3/24/24 11:30, Koteswararao Gundapaneni wrote:
> > When can I expect the update on the HTTP/3 protocol implementation?
> >
> >
> > HTTP/3
> >
> > RFC 9114 <https://datatracker.ietf.org/doc/html/rfc9114> (June 2022) -
> > HTTP/3
> >
> > Not yet implemented by Apache Tomcat. (As of July 2022)
>
> Why pick "July 2022" as an arbitrary date to be not-implemented-as-of
> instead of, say, TODAY?
>
> > https://datatracker.ietf.org/doc/html/rfc9114#section-1.1-2
>
> (This reference doesn't seem relevant.)
>
> h3 is not currently a priority for the Apache Tomcat team, for several
> reasons:
>
> 1. Tomcat is very often used behind a reverse proxy, where persistent
> HTTP or h2 connections can be used to "solve" the
> connection-establishment "problem".
>
> 2. Java does not currently provide an implementation of h3. This means
> we either have to wait for Java to provide such an implementation or
> look to outside libraries such as Quiche. One of the goals of Tomcat is
> to have as few dependencies as possible, so using Quiche, etc. would be
> contrary to those goals.
>
> 3. OpenSSL currently does provide an implementation of h3 but it is very
> different than both the current implementation of TLS and also anything
> offered by Java (which does not yet exist).
>
> This is a project run by a small group of volunteers, not a large
> company with many resources. We all have "day jobs" where we spend most
> of our time.
>
> You've been making inquiries about becoming a committer on the project.
> One way to score a lot of points towards that might be to propose a
> working implementation of h3 that can be added to a currently-supported
> version of Tomcat. I would encourage you to work exclusively on the 11.x
> branch, as that is where most new functionality is added before being
> back-ported to the other stable branches.
>
> -chris
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
> For additional commands, e-mail: dev-h...@tomcat.apache.org
>
>

HTTP / 3 protocol updates

[Koteswararao Gundapaneni]

When can I expect the update on the HTTP/3 protocol implementation?


HTTP/3

RFC 9114  (June 2022) -
HTTP/3

Not yet implemented by Apache Tomcat. (As of July 2022)


https://datatracker.ietf.org/doc/html/rfc9114#section-1.1-2

regards,
Koti

Re: Instruct the tomcat source builders before the build process for tomcat source 8.5.100

[Koteswararao Gundapaneni]

On Fri, Mar 22, 2024 at 4:09 AM Mark Thomas  wrote:

> On 22/03/2024 10:54, Koteswararao Gundapaneni wrote:
> > Hi,
> >
> > While building the tomcat source 8.5.100 its giving an error with java 7
> >
> > below is the error
> >
> > ANT_OPTS is set to  -Djava.security.manager=allow
> > Error occurred during initialization of VM
> > java.lang.UnsupportedClassVersionError: allow : Unsupported major.minor
> > version 52.0
> >
> > in Building.txt file it has the following instruction
> >
> >   3. Install the JDK according to the instructions included with the
> release.
> >
> > so if am not wrong, we could suggest java11 is required for the build
> > process in the instructions given
>
> Yes, you are wrong.
>
> PLEASE read the documentation first. Specifically this sentence from
> BUILDING.txt
>
> 
> Download a version 11 or later of Java Development Kit...
> 
>
> Mark
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
> For additional commands, e-mail: dev-h...@tomcat.apache.org
>
> The above quote is  not available in BUILDING.txt:

FYI: added BUILDING.txt

  Licensed to the Apache Software Foundation (ASF) under one or more
  contributor license agreements.  See the NOTICE file distributed with
  this work for additional information regarding copyright ownership.
  The ASF licenses this file to You under the Apache License, Version 2.0
  (the "License"); you may not use this file except in compliance with
  the License.  You may obtain a copy of the License at

  http://www.apache.org/licenses/LICENSE-2.0

  Unless required by applicable law or agreed to in writing, software
  distributed under the License is distributed on an "AS IS" BASIS,
  WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
  See the License for the specific language governing permissions and
  limitations under the License.



Building The Apache Tomcat @VERSION_MAJOR_MINOR@ Servlet/JSP 
Container


This project contains the source code for Tomcat @VERSION_MAJOR_MINOR@, a 
container that
implements the Servlet @SERVLET_SPEC_VERSION@, JSP @JSP_SPEC_VERSION@, EL 
@EL_SPEC_VERSION@, WebSocket @WEBSOCKET_SPEC_VERSION@ and JASPIC 
@JASPIC_SPEC_VERSION@
specifications from the Java Community Process <https://www.jcp.org/>.

Note: If you just need to run Apache Tomcat, it is not necessary to build
it. You may simply download a binary distribution. It is cross-platform.
Read RUNNING.txt for the instruction on how to run it.

In order to build a binary distribution version of Apache Tomcat from a
source distribution, do the following:


(1) Download and Install a Java Development Kit

 1. If the JDK is already installed, skip to (2).

 2. Download a version @BUILD_JAVA_VERSION@ or later of Java Development Kit 
(JDK) release (use
the latest update available for your chosen version) from one of:

http://www.oracle.com/technetwork/java/javase/downloads/index.html
http://openjdk.java.net/install/index.html
or another JDK vendor.

Note regarding later versions of Java:

  As documented elsewhere, one of components in Apache Tomcat includes
  a private copy of the Apache Commons DBCP 2 library.

  The JDBC interfaces implemented by DBCP frequently change in non-backwards
  compatible ways between versions of the Java SE specification. Therefore,
  it is likely that DBCP 2 will only compile with the specific version of 
Java
  listed above and that compilation will fail if a later version of Java is
  used.

  See Apache Commons DBCP 2 project web site for more details on
  available versions of the library and its requirements,

https://commons.apache.org/dbcp/

 3. Install the JDK according to the instructions included with the release.

 4. Set an environment variable JAVA_HOME to the pathname of the directory
into which you installed the JDK release.


(2) Install Apache Ant version @ANT_VERSION_REQUIRED@ or later on your computer.

 1. If Apache Ant version @ANT_VERSION_REQUIRED@ or later is already installed 
on your
computer, skip to (3).

 2. Download a binary distribution of Ant from:

https://ant.apache.org/bindownload.cgi

 3. Unpack the binary distribution into a convenient location so that the
Ant release resides in its own directory (conventionally named
"apache-ant-[version]").

For the purposes of the remainder of this document, the symbo

Re: Plans for 10.1.x and 8.5.x release?

[Koteswararao Gundapaneni]

Hi

Innovations are on the way for both 10.1.x and 8.5.x

regards,
Koti

On Fri, Mar 15, 2024 at 4:53 AM Mark Thomas  wrote:

> Chris,
>
> Just wondering what your thinking was for the March releases of 10.1.x
> and 8.5.x
>
> Mark
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
> For additional commands, e-mail: dev-h...@tomcat.apache.org
>
>

Welcome note

[Koteswararao Gundapaneni]

Hi

I will be act from now onwards as a good contributor with the new mailing
address provided.


regards,
Koti