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

            Bug ID: 60014
           Summary: Nio2 Connector with SLL (OpenSSL) truncates post data
           Product: Tomcat 8
           Version: 8.5.4
          Hardware: PC
                OS: Linux
            Status: NEW
          Severity: major
          Priority: P2
         Component: Connectors
          Assignee: dev@tomcat.apache.org
          Reporter: a.vett...@b2bires.com

Hello,
here's the environment :

Linux 3.10.0-327.el7.x86_64 #1 SMP

Java(TM) SE Runtime Environment (build 1.8.0_101-b13)
Java HotSpot(TM) 64-Bit Server VM (build 25.101-b13, mixed mode)

Tomcat 8.5.4

    <Connector port="8443"
protocol="org.apache.coyote.http11.Http11Nio2Protocol"
               executor="ttp8443"       
sslImplementationName="org.apache.tomcat.util.net.openssl.OpenSSLImplementation"
               connectionTimeout="20000"
               enableLookups="false" acceptCount="200"
               scheme="https" secure="true" SSLEnabled="true"
               SSLCertificateFile="..." SSLCertificateKeyFile="..."
SSLCertificateChainFile="..."
               compression="off" />


Problem: Our web app is an e-commerce web site, it uses various technologies
and frameworks. A few days ago we upgraded to tomcat 8.5.4 and java 8 from
tomcat 7.x and java 7. We noticed that a certain form was not working correctly
all of times (sometimes it worked, sometimes not). A large number of users had
the issue, with various browsers and operating system on the client side.
Debugging the issue I found that in some cases, not all form data arrives at
the MVC framework. It seems truncated at some point. Looking at the post data
with browser web tools I can see the entire data. Data size is small, just a
few attribute names and values.

Since on tomcat 7.x we used Apr, I tried to use the Apr Connector (changed the
protocol attribute of the connector to
org.apache.coyote.http11.Http11AprProtocol and removed the
sslImplementationName parameter) , I have not changed anything else on the
server or web app. This fixed the issue.

So my guess is that for some reason Nio2 is the cause.

If this is not a known issue, I'll try to investigate more. Please let me know.
Thanks

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

Reply via email to