Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
timeout < 30 only?
See original GitHub issueI am setting timeout to 300 seconds (to test an AWS lambda function + API Gateway), but HTTPie continues to timeout at 30 seconds. Is there an upper limit set at 30 seconds? I’´m using
http --timeout=300 POST https://...
Issue Analytics
- State:
- Created 6 years ago
- Reactions:2
- Comments:5 (1 by maintainers)
Top Results From Across the Web
what is the meaning of (timeout 30) when commit executed
Hi Experts, I have a quick question regarding (timeout 30) and how it work during commit operation. When I committed something with IOS...
Read more >Timeout should only occur if no activity for 30 minutes
config file I have tried using this code but after 30 minutes session expired while user is active(making request) on web site. 1....
Read more >Why are some NFL timeouts '30-second timeouts'? - Quora
The 30 seconds time outs are for when a team wants to just stop the clock, because they don't want the other team...
Read more >Why is screen timeout only maximum 30 min on an android ...
I own a pixel 3a (and pixel 3 xl) running the latest updates as of july 2022.I think it's kinda lame that I...
Read more >pexpect timeout is not being used, only the default of 30 is ...
It appears to work if you only specify the timeout in the .spawn call, you cannot override, or use timeout=300 in the .expect...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
This is not
httpietiming out. You’re receiving a response that tells you the intermediary between you and your lambda function is timing out the request.--timeoutis from your computer to that intermediary. The intermediary can set whatever timeout it wants from itself to your lambda function. This is firmly not an HTTPie bug.@gnulnx there’s a default 30s connection timeout which you can change via
--timeout=n.(The default timeout will be removed in v2.0.0.)