[Patch] New option --http-proxy

Christian Biere cbiere at TechFak.Uni-Bielefeld.DE
Tue Dec 9 00:14:41 CET 2003

Werner Koch wrote:
> There is a standard way to define a PROXY, used by many programs and
> we would add confusion when adding a second way of doing that.

Ok, maybe there's a way to make this option less confusing:

"keyserver-option http-proxy" would imply "use $http_proxy"


"keyserver-option http-proxy=http://proxy/" would allow to use
an explicitly given URL.

> A proxy belongs to your network configuration and a program should play
> that setting.  With an additional way of setting the proxy, you are
> required to change the proxy address at several places - that is bad
> for system admistration.

I agree partially. However, there dozens of programs which already
have their own network configuration methods. In the concerned
environment, http_proxy is unset. Not all programs might play well
with the proxy, so we don't want to change that without a very good
reason. The proxy doesn't serve request for the local domain, so just
setting http_proxy isn't a complete configuration and the programs
(mostly web browsers) have to be configured to not use the proxy
for the local domain anyways.
Also, for non-unix users http_proxy is probably only used in the
context of gpg and a "normal" option would be more straight-
forward for them.

> Regarding your patches, we can't use them without a copyright
> assignment.

I assumed patches are covered by the same license as the files to
be patched. If that's not the case, I declare this rule for my
patches with this statement.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 303 bytes
Desc: not available
Url : /pipermail/attachments/20031209/d161bc3b/attachment-0001.bin

More information about the Gnupg-devel mailing list