Merge lp:~mbp/bzr/doc into lp:bzr

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Martin Pool wrote:
> Martin Pool has proposed merging lp:~mbp/bzr/doc into lp:bzr.
>
> Requested reviews:
> bzr-core (bzr-core)
> Related bugs:
> #398653 Releasing guide should include instructions on updating trunk NEWS file
> https://bugs.launchpad.net/bugs/398653
> #473099 Incorrect markup in centralized workflow tutorial
> https://bugs.launchpad.net/bugs/473099
> #512385 Broken link to "quick start card" in online user guide
> https://bugs.launchpad.net/bugs/512385
>
>
> Document proxy settings, from https://bugs.edge.launchpad.net/bzr/+bug/186920/comments/56
>

If you're going to be documenting http[s]_proxy shouldn't you also
document no_proxy, all_proxy, and the rest?

John
=:->

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (Cygwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAkwzO1QACgkQJdeBCYSNAAMCFgCfRDukTgzdRK5Vj89SL1s5XS3t
cpAAnRIfI4AQQ+673+fY+/TBUt8Sfxq6
=72PG
-----END PGP SIGNATURE-----

On 7 July 2010 00:21, John A Meinel <email address hidden> wrote:
> If you're going to be documenting http[s]_proxy shouldn't you also
> document no_proxy, all_proxy, and the rest?

Good point. I didn't actually know about them. Where are they defined?

--
Martin

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Martin Pool wrote:
> On 7 July 2010 00:21, John A Meinel <email address hidden> wrote:
>> If you're going to be documenting http[s]_proxy shouldn't you also
>> document no_proxy, all_proxy, and the rest?
>
> Good point. I didn't actually know about them. Where are they defined?
>

Vincent would know better than myself. There is some documentation here:
  http://docs.python.org/library/urllib.html

The urlopen() function works transparently with proxies which do not
require authentication. In a Unix or Windows environment, set the
http_proxy, or ftp_proxy environment variables to a URL that identifies
the proxy server before starting the Python interpreter. For example
(the '%' is the command prompt):

% http_proxy="http://www.someproxy.com:3128"
% export http_proxy
% python
...

The no_proxy environment variable can be used to specify hosts which
shouldn’t be reached via proxy; if set, it should be a comma-separated
list of hostname suffixes, optionally with :port appended, for example
cern.ch,ncsa.uiuc.edu,some.host:8080.

In a Windows environment, if no proxy environment variables are set,
proxy settings are obtained from the registry’s Internet Settings section.

I think 'all_proxy' is used for both http, https and ftp. 'no_proxy'
allows you to have a 'match everything' http proxy, except for
internal-only websites, etc.

John
=:->
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (Cygwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAkwz0VkACgkQJdeBCYSNAAPcpACgpPZ/aZHi2bz5e7iO80Yh3EmW
dqgAoKXmeoLuACBKOhIqHG7rnkqNnaR6
=o/j0
-----END PGP SIGNATURE-----

On 7 July 2010 11:01, John A Meinel <email address hidden> wrote:
> I think 'all_proxy' is used for both http, https and ftp. 'no_proxy'
> allows you to have a 'match everything' http proxy, except for
> internal-only websites, etc.

I didn't want to add ftp_proxy or all_proxy etc because I'm not sure
that they actually do work for all protocols with bzr. Perhaps they
actually do.

--
Martin

sent to pqm by email

>>>>> Martin Pool <email address hidden> writes:

    > On 7 July 2010 11:01, John A Meinel <email address hidden> wrote:
    >> I think 'all_proxy' is used for both http, https and ftp. 'no_proxy'
    >> allows you to have a 'match everything' http proxy, except for
    >> internal-only websites, etc.

Correct.

    > I didn't want to add ftp_proxy or all_proxy etc because I'm not sure
    > that they actually do work for all protocols with bzr. Perhaps they
    > actually do.

I don't think the ftp transport (via ftplib) respect that (quick search
for proxy in ftplib confims that).

So intead of 'Perhaps they actually do' may be its 'Perhaps they
actually should' :-/

         Vincent