ywkaras opened a new issue, #9537: URL: https://github.com/apache/trafficserver/issues/9537
In this PR: https://github.com/apache/trafficserver/pull/9518/files If I comment out this test run in `tls_tunnel.test.py`: ``` ''' tr = Test.AddTestRun("test {inbound_local_port}") tr.Processes.Default.Command = "curl -vvv --resolve 'incoming.port.com:{0}:127.0.0.1' -k https://incoming.port.com:{0}".format( ts.Variables.ssl_port) # The tunnel connecting to the outgoing port which is the same as the incoming # port (per the `inbound_local_port` configuration) will result in ATS # connecting back to itself. This will result in a connection close and a # non-zero return code from curl. In production, the server will listen on the # same port as ATS but have a different IP. tr.ReturnCode = 35 tr.StillRunningAfter = ts ts.Disk.traffic_out.Content += Testers.ContainsExpression( f"CONNECT tunnel://backend.incoming.port.com:{ts.Variables.ssl_port} HTTP/1.1", "Verify a CONNECT request is handled") ts.Disk.traffic_out.Content += Testers.ContainsExpression("HTTP/1.1 400 Direct self loop detected", "The loop should be detected") ''' ``` The value of `proxy.process.http.connect_requests` (read at the end of the test) drops from 10 to 7. This is the verbose output of the curl command in this test run: ``` * Added incoming.port.com:61002:127.0.0.1 to DNS cache * Hostname incoming.port.com was found in DNS cache * Trying 127.0.0.1:61002... % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed ^M 0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0* Connected to incoming.port.com (127.0.0.1) port 61002 (#0) * ALPN: offers h2 * ALPN: offers http/1.1 } [5 bytes data] * TLSv1.3 (OUT), TLS handshake, Client hello (1): } [512 bytes data] * error:1408F10B:SSL routines:ssl3_get_record:wrong version number ^M 0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0 * Closing connection 0 curl: (35) error:1408F10B:SSL routines:ssl3_get_record:wrong version number ``` -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
