ERROR: Proxy response is unexpectedly large and cannot fit in the 128-bytes buffer.

[dansto]

Is it possible to fix this?

DEBUG: openfortivpn 1.21.0
DEBUG: revision unavailable
DEBUG: Loaded configuration file "/etc/openfortivpn/config".
VPN account password:
DEBUG: Configuration host = ""
DEBUG: Configuration realm = ""
DEBUG: Configuration port = "443"
DEBUG: Configuration username = ""
DEBUG: Resolving gateway host ip
DEBUG: Establishing ssl connection
DEBUG: SO_KEEPALIVE: OFF
DEBUG: TCP_KEEPIDLE: 240
DEBUG: TCP_KEEPINTVL: 10
DEBUG: TCP_KEEPCNT: 6
DEBUG: SO_SNDBUF: 16384
DEBUG: SO_RCVBUF: 131072
DEBUG: proxy_host: ********
DEBUG: proxy_port: 80
DEBUG: server_addr: *******
DEBUG: server_port: 80
DEBUG: gateway_ip: ******
DEBUG: gateway_port: 443
ERROR: Proxy response is unexpectedly large and cannot fit in the 128-bytes buffer.
INFO: Closed connection to gateway.
DEBUG: SO_KEEPALIVE: OFF
DEBUG: TCP_KEEPIDLE: 240
DEBUG: TCP_KEEPINTVL: 10
DEBUG: TCP_KEEPCNT: 6
DEBUG: SO_SNDBUF: 16384
DEBUG: SO_RCVBUF: 131072
DEBUG: proxy_host: **********
DEBUG: proxy_port: 80
DEBUG: server_addr: ***********
DEBUG: server_port: 80
DEBUG: gateway_ip: ********
DEBUG: gateway_port: 443
ERROR: Proxy response is unexpectedly large and cannot fit in the 128-bytes buffer.
INFO: Could not log out.

[DimitriPapadopoulos]

This is where the error occurs:

openfortivpn/src/tunnel.c

Lines 761 to 762 in f778df2

	if (env_proxy != NULL) {
	char request[128];

openfortivpn/src/tunnel.c

Lines 785 to 787 in f778df2

	if (j >= ARRAY_SIZE(request) - 1) {
	log_error("Proxy response is unexpectedly large and cannot fit in the %lu-bytes buffer.\n",
	ARRAY_SIZE(request));

I can increase of the buffer from 128 to say 1024 as a workaround, but obviously it's best to use code that consumes the response in chunks, or parses the Content-Length in the header to adapt the size of the buffer. Maybe there's already such code in openfortivpn, I cannot recall right now.

[DimitriPapadopoulos]

#1309 increases the maximum size of the proxy response from 128 to 4096.

Again, this is not a real fix, just a work around. It should fit the vast majority of use cases.