Re^4: How to make an HTTP request with an equivalent of curl's --max-time?

No, not for the self-explanatory option

It would be self-explanatory if its name was max-seconds, that's the problem with most of the _time / -time variables and options. Very few things these days are self explanatory, and, due to insufficient information provided, one often has to figure out the units, the limits, or even the object of a question. ;)

for the magic url that is immune to regular HTTP GET, that it needs a client induced timeout

The OP (probably) refers to the Twitter streaming API - here is the documentation you were (probably) asking for. There are multiple requirements forced upon the client of the stream, like this one below (quote from the docs):

Set a timer, either a 90 second TCP level socket timeout, or a 90 second application level timer on the receipt of new data. If 90 seconds pass with no data received, including newlines, disconnect and reconnect immediately according to the backoff strategies in the next section. The Streaming API will send a keep-alive newline every 30 seconds to prevent your application from timing out the connection. You should wait at least 3 cycles to prevent spurious reconnects in the event of network congestion, local CPU starvation, local GC pauses, etc.

- Luke

Comment on Re^4: How to make an HTTP request with an equivalent of curl's --max-time? Download Code

Replies are listed 'Best First'.
Re^5: How to make an HTTP request with an equivalent of curl's --max-time? by Anonymous Monk on Jan 14, 2015 at 09:20 UTC
LWP timeout option is for seconds of TCP level socket timeout ... default is 120 seconds not 90	[reply]
Re^6: How to make an HTTP request with an equivalent of curl's --max-time? by blindluke (Hermit) on Jan 14, 2015 at 09:31 UTC
The quote I posted comes from the Twitter documentation (that I linked to in my reply). This has nothing to do with the defaults of the LWP module. The value specified by the streaming API is 90 seconds. I have not written a single word in this thread about LWP and the default values it uses for its options. - Luke	[reply]
Re^7: How to make an HTTP request with an equivalent of curl's --max-time? by Anonymous Monk on Jan 14, 2015 at 10:15 UTC
The quote I posted ... obvious self evident things .. Yes, this is true, you have revealed the source of the OPs requirement, and I explained that LWP provides timeout to satisfy the requirement as laid out in those docs you quoted ... no real need for a max-time when a socket timeout is adequate	[reply]
Re^8: How to make an HTTP request with an equivalent of curl's --max-time? by blindluke (Hermit) on Jan 14, 2015 at 10:52 UTC
Re^9: How to make an HTTP request with an equivalent of curl's --max-time? by Anonymous Monk on Jan 14, 2015 at 10:55 UTC
Re^9: How to make an HTTP request with an equivalent of curl's --max-time? by Cody Fendant (Hermit) on Jan 14, 2015 at 22:24 UTC


Come for the quick hacks, stay for the epiphanies.
	PerlMonks