HTTP Proxy responses are logged char by char
Dear forum readers,
I am experiencing a strange behavior when logging is enabled and HTTP proxy is enabled. The responses returned by the HTTP proxy seems to be written to the log file as if it were constructed char by char. Here is an example, because it is difficult for me to describe in english...
. 2018-02-19 22:26:20.463 --------------------------------------------------------------------------
. 2018-02-19 22:26:20.479 Connecting to host.domain.com ...
. 2018-02-19 22:26:20.510 HTTP proxy command: CONNECT host.domain.com:21 HTTP/1.1
. 2018-02-19 22:26:20.510 Host: host.domain.com:21
. 2018-02-19 22:26:20.510
. 2018-02-19 22:26:20.510 Connection with proxy established, performing handshake...
. 2018-02-19 22:26:20.573 HTTP proxy response: HTTP/1.0 200 Connection established
. 2018-02-19 22:26:20.573 HTTP proxy response: HTTP/1.0 200 Connection established
. 2018-02-19 22:26:20.573 X
. 2018-02-19 22:26:20.573 HTTP proxy response: HTTP/1.0 200 Connection established
. 2018-02-19 22:26:20.573 X-
. 2018-02-19 22:26:20.573 HTTP proxy response: HTTP/1.0 200 Connection established
. 2018-02-19 22:26:20.573 X-B
. 2018-02-19 22:26:20.573 HTTP proxy response: HTTP/1.0 200 Connection established
. 2018-02-19 22:26:20.573 X-Bs
. 2018-02-19 22:26:20.573 HTTP proxy response: HTTP/1.0 200 Connection established
. 2018-02-19 22:26:20.573 X-Bst
. 2018-02-19 22:26:20.573 HTTP proxy response: HTTP/1.0 200 Connection established
. 2018-02-19 22:26:20.573 X-Bst-
. 2018-02-19 22:26:20.573 HTTP proxy response: HTTP/1.0 200 Connection established
.....More lines.....
. 2018-02-19 22:26:20.573 X-Bst-Request-Id: r
. 2018-02-19 22:26:20.573 HTTP proxy response: HTTP/1.0 200 Connection established
.....
At the end, if the response has about 100 characters, I get 300 lines in the log file for each response, which makes quite difficult to review it (apart from waste of space).
I noticed this behaviour on version 5.11.2, and I have verified that version 5.13 still exhibit the same problem.
Have you found a similar behavior?
Is there something I can do to avoid it?
This is my WinSCP command:
Any help will be appreciated
I am experiencing a strange behavior when logging is enabled and HTTP proxy is enabled. The responses returned by the HTTP proxy seems to be written to the log file as if it were constructed char by char. Here is an example, because it is difficult for me to describe in english...
. 2018-02-19 22:26:20.463 --------------------------------------------------------------------------
. 2018-02-19 22:26:20.479 Connecting to host.domain.com ...
. 2018-02-19 22:26:20.510 HTTP proxy command: CONNECT host.domain.com:21 HTTP/1.1
. 2018-02-19 22:26:20.510 Host: host.domain.com:21
. 2018-02-19 22:26:20.510
. 2018-02-19 22:26:20.510 Connection with proxy established, performing handshake...
. 2018-02-19 22:26:20.573 HTTP proxy response: HTTP/1.0 200 Connection established
. 2018-02-19 22:26:20.573 HTTP proxy response: HTTP/1.0 200 Connection established
. 2018-02-19 22:26:20.573 X
. 2018-02-19 22:26:20.573 HTTP proxy response: HTTP/1.0 200 Connection established
. 2018-02-19 22:26:20.573 X-
. 2018-02-19 22:26:20.573 HTTP proxy response: HTTP/1.0 200 Connection established
. 2018-02-19 22:26:20.573 X-B
. 2018-02-19 22:26:20.573 HTTP proxy response: HTTP/1.0 200 Connection established
. 2018-02-19 22:26:20.573 X-Bs
. 2018-02-19 22:26:20.573 HTTP proxy response: HTTP/1.0 200 Connection established
. 2018-02-19 22:26:20.573 X-Bst
. 2018-02-19 22:26:20.573 HTTP proxy response: HTTP/1.0 200 Connection established
. 2018-02-19 22:26:20.573 X-Bst-
. 2018-02-19 22:26:20.573 HTTP proxy response: HTTP/1.0 200 Connection established
.....More lines.....
. 2018-02-19 22:26:20.573 X-Bst-Request-Id: r
. 2018-02-19 22:26:20.573 HTTP proxy response: HTTP/1.0 200 Connection established
.....
At the end, if the response has about 100 characters, I get 300 lines in the log file for each response, which makes quite difficult to review it (apart from waste of space).
I noticed this behaviour on version 5.11.2, and I have verified that version 5.13 still exhibit the same problem.
Have you found a similar behavior?
Is there something I can do to avoid it?
This is my WinSCP command:
WinSCP.exe /log="%logPath%\RX-%dt%.log" /ini=nul /command "option batch abort" "option confirm off" "open ftp://user:password@host.domain.com/ -rawsettings ProxyMethod=3 ProxyHost=proxy.proxydomain.com ProxyPort=8081" "cd \OUT\" "get -delete * %dataPath%\files\rem2loc\*.txt" "exit"
Any help will be appreciated