3 ms·
Just to be clear, you're trying to run the program from behind a proxy, yeah? Thanks for the stack trace -- having that makes a big difference :) I'm not sure
by scottjackson 17y ago
Just to be clear, you're trying to run the program from behind a proxy, yeah?
Thanks for the stack trace -- having that makes a big difference :)
I'm not sure I can make it work with an arbitrary proxy, but I'm pretty sure I could get it to work with a proxy you know the address of. Proxies aren't my strong suit, sorry. We'll see what happens!
- RyanMcGreal 17y ago> you're trying to run the program from behind a proxy, yeah? That's right. > I'm not sure I can make it work with an arbitrary proxy You could assume that users know their own proxy address (e.g. http://proxy.domain.com:80 http://proxy.domain.com:80) and offer a prompt for them to input it. Then you can just save it in the config file. I added an update to the stack trace page with some code for working with proxies: http://quandyfactory.com/projects/32/stack_trace_for_hnshpy_on_proxy http://quandyfactory.com/projects/32/stack_trace_for_hnshpy_... Hope that helps!
- scottjackson 17y agoThanks a bunch! It's getting pretty late now (just hit 3am), but check back at http://github.com/scottjacksonx/hnsh http://github.com/scottjacksonx/hnsh (or http://scottjackson.org/software/hnsh/ http://scottjackson.org/software/hnsh/) some time late tomorrow and the project should be hosted there, as well as your proxy fix.
- RyanMcGreal 17y agoGreat stuff! I'll follow your github repository.