bneradt commented on issue #1652:
URL: https://github.com/apache/trafficserver/issues/1652#issuecomment-825988469


   @esmq2092 : Thank you for filing this issue.
   
   I've added a few tests where ATS is configured to not respond with chunked 
content and the client initiates the transaction with "Connection: Keep-Alive":
   https://github.com/apache/trafficserver/pull/7743
   
   ATS seems to behave as expected:
   * It does not reply with a chunked-encoded response.
   * It includes a connection-close header.
   
   Our Proxy Verifier test client experiences no issues with the responses.
   
   My first request to you: **can you please review that test in the PR, 
looking particularly at the ATS configuration, and verify that it has the 
configuration you expect would be needed to reproduce the problem you explain 
here?** I believe it does per my reading of this issue, but it wouldn't hurt to 
double-check my work.
   
   Second: with this configuration, I also tried reproducing the wget issue you 
experienced by performing requests against ATS proxying to this same test 
server. It had the same configuration, and the test server replied with a 
chunked response. I could not reproduce the issue though. In addition to 
checking my ATS configuration, **can you please provide me your wget command 
line invocation**? Here was mine:
   
   ```
   $ wget --version
   GNU Wget 1.14 built on linux-gnu.
   
   +digest +https +ipv6 +iri +large-file +nls +ntlm +opie +ssl/openssl 
   
   Wgetrc: 
       /etc/wgetrc (system)
   Locale: /usr/share/locale 
   Compile: gcc -DHAVE_CONFIG_H -DSYSTEM_WGETRC="/etc/wgetrc" 
       -DLOCALEDIR="/usr/share/locale" -I. -I../lib -I../lib -O2 -g -pipe 
       -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector-strong 
       --param=ssp-buffer-size=4 -grecord-gcc-switches -m64 -mtune=generic 
   Link: gcc -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions 
       -fstack-protector-strong --param=ssp-buffer-size=4 
       -grecord-gcc-switches -m64 -mtune=generic -lssl -lcrypto 
       /usr/lib64/libssl.so /usr/lib64/libcrypto.so /usr/lib64/libz.so 
       -ldl -lz -lz -lidn -luuid -lpcre ftp-opie.o openssl.o http-ntlm.o 
       ../lib/libgnu.a 
   
   Copyright (C) 2011 Free Software Foundation, Inc.
   License GPLv3+: GNU GPL version 3 or later
   <http://www.gnu.org/licenses/gpl.html>.
   This is free software: you are free to change and redistribute it.
   There is NO WARRANTY, to the extent permitted by law.
   
   Originally written by Hrvoje Niksic <[email protected]>.
   Please send bug reports and questions to <[email protected]>.
   
   $ wget --header "uuid: 2" --header "Connection: Keep-Alive" 
--no-check-certificate https://localhost:61012/for/https                        
                                                                                
                       
   --2021-04-23 23:14:48--  https://localhost:61012/for/https
   Resolving localhost (localhost)... ::1, 127.0.0.1
   Connecting to localhost (localhost)|::1|:61012... failed: Connection refused.
   Connecting to localhost (localhost)|127.0.0.1|:61012... connected.
   WARNING: cannot verify localhost's certificate, issued by 
‘/C=IE/ST=Dublin/L=Dublin/O=example.com/OU=example.com/CN=example.com’:
     Self-signed certificate encountered.
       WARNING: certificate common name ‘example.com’ doesn't match requested 
host name ‘localhost’.
   HTTP request sent, awaiting response... 200 OK
   Length: unspecified
   Saving to: ‘https’
   
       [ <=>                                                                    
                                                                                
                                                  ] 32          --.-K/s   in 0s 
     
   
   2021-04-23 23:14:48 (1.63 MB/s) - ‘https’ saved [32]
   
   $ cat https
   0000000 0000001 0000002 0000003 $
   ```
   
   As you can see, I have wget 1.14 instead of 1.16. I'm not sure whether that 
could be the significant difference.


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

For queries about this service, please contact Infrastructure at:
[email protected]


Reply via email to