# Re: pybombs/wget behind a proxy

**URL:** <https://www.ruby-forum.com/t/re-pybombs-wget-behind-a-proxy/238556>\
**Category:** GNU Radio\
**Created:** [January 16, 2014, 6:20pm UTC](https://www.ruby-forum.com/t/re-pybombs-wget-behind-a-proxy/238556 "2014-01-16T18:20:48Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![musicdenotation](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/m/ea666f/32.png) [@musicdenotation](https://www.ruby-forum.com/u/musicdenotation)\
**Post date:** [January 16, 2014, 6:20pm UTC](https://www.ruby-forum.com/t/re-pybombs-wget-behind-a-proxy/238556/1 "2014-01-16T18:20:48Z")

</div>

Alex,

I’m inclined to make this timeout a Pybombs configuration variable that  
defaults to 10. I think for most people that is a reasonable timeout  
value, but this would make it very easy for it to be bumped up in  
special circumstances such as yours. Does this sound reasonable to  
you?

Tim

-------- Original message --------  
From: Alexandru C. [removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid)  
Date:01/16/2014 10:43 (GMT-05:00)  
To: removed\_email\_address@domain.invalid  
Subject: [Discuss-gnuradio] pybombs/wget behind a proxy

Greetings,

There seems to be a 10 second timeout when pybombs fetches packages  
using wget. This is way too short when working behind a proxy.

I have no clue how proxies are supposed to work. The one I am sitting  
behind downloads the package and scans it for viruses and during that  
time the connection appears to hang from wget point of view. With a  
large package like Ice, 10 seconds are not sufficient. I don’t know  
what a proper timeout would be, but maybe this is why the default  
timeout is so long.

Alex

---

<div class="post-metadata">

**Author:** ![tim](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/t/ce73a5/32.png) [@tim](https://www.ruby-forum.com/u/tim)\
**Post date:** [January 16, 2014, 8:16pm UTC](https://www.ruby-forum.com/t/re-pybombs-wget-behind-a-proxy/238556/2 "2014-01-16T20:16:43Z")

</div>

Hi Tim,

I think that will be a good solution. Thanks.

Alex
