Proxy-Timeout with WebApp-Push

Targets Web
1

Hi,

for years, Xojo Webapps, are spamming my Proxy-Error Logs.
The WebApp is running as Standalone on a dedicated machine.
Another machine “in front” is working as Apache-Proxy and doing https.

Client <-https-> Proxy <-http-> Xojo-Webapps-Server

The Webapps seems to use open connection to do communication with the client.
The Proxy closes these connections after a timeout of (seems like) 65 seconds.

Is that real websocket? could it be handled by mod_proxy_wstunnel?

[Mon Apr 16 19:38:46.538030 2018] [proxy_http:error] [pid 93707] (70007)The timeout specified has expired: [client 2003:a:407:7400:a189:560a:3883:f7df:64569] AH01102: error reading status line from remote server 192.168.200.240:8001, referer: http://fppersonal.aoda-it.de/ [Mon Apr 16 19:38:46.538090 2018] [proxy:error] [pid 93707] [client 2003:a:407:7400:a189:560a:3883:f7df:64569] AH00898: Error reading from remote server returned by /DD3053306D9727CE6280194B7B9D4A84ED991ED6/comm/push, referer: http://fppersonal.aoda-it.de/ [Mon Apr 16 19:39:51.561309 2018] [proxy_http:error] [pid 93707] (70007)The timeout specified has expired: [client 2003:a:407:7400:a189:560a:3883:f7df:64569] AH01102: error reading status line from remote server 192.168.200.240:8001, referer: http://fppersonal.aoda-it.de/ [Mon Apr 16 19:39:51.561367 2018] [proxy:error] [pid 93707] [client 2003:a:407:7400:a189:560a:3883:f7df:64569] AH00898: Error reading from remote server returned by /DD3053306D9727CE6280194B7B9D4A84ED991ED6/comm/push, referer: http://fppersonal.aoda-it.de/ [Mon Apr 16 19:40:56.532040 2018] [proxy_http:error] [pid 93707] (70007)The timeout specified has expired: [client 2003:a:407:7400:a189:560a:3883:f7df:64569] AH01102: error reading status line from remote server 192.168.200.240:8001, referer: http://fppersonal.aoda-it.de/ [Mon Apr 16 19:40:56.532138 2018] [proxy:error] [pid 93707] [client 2003:a:407:7400:a189:560a:3883:f7df:64569] AH00898: Error reading from remote server returned by /DD3053306D9727CE6280194B7B9D4A84ED991ED6/comm/push, referer: http://fppersonal.aoda-it.de/ [Mon Apr 16 19:42:01.558045 2018] [proxy_http:error] [pid 93707] (70007)The timeout specified has expired: [client 2003:a:407:7400:a189:560a:3883:f7df:64569] AH01102: error reading status line from remote server 192.168.200.240:8001, referer: http://fppersonal.aoda-it.de/ [Mon Apr 16 19:42:01.558105 2018] [proxy:error] [pid 93707] [client 2003:a:407:7400:a189:560a:3883:f7df:64569] AH00898: Error reading from remote server returned by /DD3053306D9727CE6280194B7B9D4A84ED991ED6/comm/push, referer: http://fppersonal.aoda-it.de/ [Mon Apr 16 19:43:06.604033 2018] [proxy_http:error] [pid 93707] (70007)The timeout specified has expired: [client 2003:a:407:7400:a189:560a:3883:f7df:64569] AH01102: error reading status line from remote server 192.168.200.240:8001, referer: http://fppersonal.aoda-it.de/ [Mon Apr 16 19:43:06.604103 2018] [proxy:error] [pid 93707] [client 2003:a:407:7400:a189:560a:3883:f7df:64569] AH00898: Error reading from remote server returned by /DD3053306D9727CE6280194B7B9D4A84ED991ED6/comm/push, referer: http://fppersonal.aoda-it.de/ [Mon Apr 16 19:44:11.526039 2018] [proxy_http:error] [pid 93707] (70007)The timeout specified has expired: [client 2003:a:407:7400:a189:560a:3883:f7df:64569] AH01102: error reading status line from remote server 192.168.200.240:8001, referer: http://fppersonal.aoda-it.de/ [Mon Apr 16 19:44:11.526099 2018] [proxy:error] [pid 93707] [client 2003:a:407:7400:a189:560a:3883:f7df:64569] AH00898: Error reading from remote server returned by /DD3053306D9727CE6280194B7B9D4A84ED991ED6/comm/push, referer: http://fppersonal.aoda-it.de/

2

They’re not websockets. It’s what’s considered a long poll.

Basically, the browser opens a GET request and the web app doesn’t write to the connection and close it until it has something to write… or a timeout occurs. When the connection closes, the browser makes a new one.

FWIW, for all browsers except IE, we switched to a newer protocol called EventSource in 2018r1 which instead of holding those connections open all the time, the browsers make quick little connections every 3 seconds or so. The frequency is completely up to the browser and depends largely on device capability, network speed and battery power. It’s much easier on the server and allows many more concurrent users than the long poll system did.

3

Do you mean 2017r3?

4

Corrected. 2018r1.