I was wondering if anyone else has experienced this particular issue when interfacing with the smsbox HTTP connection.
I perform a standard HTTP GET request with the required information and get a "Sent" in response. This would appear to indicate normal behaviour. However, occasionally when I perform a series of connections one after the other (in quite quick succession [software automated]), smsbox indicates it receives the connection, but closes the connection as soon as it opens it, thus ignoring any HTTP request I may have wanted to perform. Normal smsbox output might be: 2001-12-17 00:04:17 [2] DEBUG: HTTP: Creating HTTPClient for `192.168.128.19'. 2001-12-17 00:04:17 [3] INFO: smsbox: Got HTTP request </cgi-bin/sendsms> from <192.168.128.19> 2001-12-17 00:04:17 [3] INFO: /sendsms used by <dotwap> 2001-12-17 00:04:17 [3] INFO: /cgi-bin/sendsms sender:<dotwap:0416905131> (192.168.128.19) to:<0417130684> msg:<Testing...> 2001-12-17 00:04:17 [3] DEBUG: Status: 202 Answer: <Sent.> 2001-12-17 00:04:17 [3] DEBUG: HTTP: Destroying HTTPClient area 0x81aa2e8. 2001-12-17 00:04:17 [3] DEBUG: HTTP: Destroying HTTPClient for `192.168.128.19'. When it ignores the connections it looks like this: 2001-12-07 07:14:56 [2] DEBUG: HTTP: Creating HTTPClient for `192.168.128.19'. 2001-12-07 07:14:56 [1] DEBUG: HTTP: Destroying HTTPClient area 0x81aa9d0. 2001-12-07 07:14:56 [1] DEBUG: HTTP: Destroying HTTPClient for `192.168.128.19'.2001-12-07 07:14:56 [2] DEBUG: HTTP: Creating HTTPClient for `192.168.128.19'. 2001-12-07 07:14:56 [1] DEBUG: HTTP: Destroying HTTPClient area 0x8198d28. 2001-12-07 07:14:56 [1] DEBUG: HTTP: Destroying HTTPClient for `192.168.128.19'.2001-12-07 07:14:57 [2] DEBUG: HTTP: Creating HTTPClient for `192.168.128.19'. 2001-12-07 07:14:57 [1] DEBUG: HTTP: Destroying HTTPClient area 0x818f6b8. 2001-12-07 07:14:57 [1] DEBUG: HTTP: Destroying HTTPClient for `192.168.128.19'. and so on. Does anyone know how to avoid this issue? Is there a maximum rate for consecutive connects to the HTTP port? Please help
