News:

  • October 15, 2026, 12:32:25 AM

Login with username, password and session length

Author Topic: HTTPCMD Timeout  (Read 65 times)

JeffS

  • Hero Member
  • *****
  • Posts: 114
HTTPCMD Timeout
« on: October 13, 2026, 03:58:26 PM »
What are the chances this timeout could be editable?

I have some busier PLCs that seem to struggle doing some of the TLS stuff within the 30 second timeframe.  Typical scan times aren't crazy but average 11-12ms which based on wireshark data has the TLS response computation right at 30 seconds.  If I manually suspend programs to lower my scantime then the HTTPS completes within the 30 second timeout.

BobO

  • Host Moderator
  • Hero Member
  • *****
  • Posts: 6177
  • Yes Pinky, Do-more will control the world!
Re: HTTPCMD Timeout
« Reply #1 on: October 14, 2026, 08:55:54 PM »
What are the chances this timeout could be editable?

I have some busier PLCs that seem to struggle doing some of the TLS stuff within the 30 second timeframe.  Typical scan times aren't crazy but average 11-12ms which based on wireshark data has the TLS response computation right at 30 seconds.  If I manually suspend programs to lower my scantime then the HTTPS completes within the 30 second timeout.

I'm sure it could be, it's hard coded now. At the least we could make it accessible via DEVREAD/DEVWRITE.

A big concern is how tolerant the server is when the TLS handshake goes long. Many servers drop the connection at 15 seconds.
"It has recently come to our attention that users spend 95% of their time using 5% of the available features. That might be relevant." -BobO