Git development
 help / color / mirror / Atom feed
From: Matthias Urlichs <smurf@smurf.noris.de>
To: Martin Langhoff <martin.langhoff@gmail.com>
Cc: Junio C Hamano <junkio@cox.net>,
	Martin Langhoff <martin@ng.eduforge.org>,
	Sven Verdoolaege <skimo@kotnet.org>,
	git@vger.kernel.org
Subject: Re: cvsimport using proxy?
Date: Wed, 5 Oct 2005 14:50:55 +0200	[thread overview]
Message-ID: <20051005125055.GF4682@kiste.smurf.noris.de> (raw)
In-Reply-To: <46a038f90510050309t1d075d7fj37c60a6052ec62f3@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 974 bytes --]

Hi,

Martin Langhoff:
> For the second stage, we'll need to hack CVSConn::conn() method around
> line 118. As I have never used the proxy option, I did a bit of
> googling. It seems that cvs 1.12.11 knows how to tunnel its protocol
> over an HTTP proxy.
> 
HTTP proxies are quite simple, you say 

   1. Connect to Proxy Server.
   2. Issue CONNECT Host:Port HTTP/1.1<CR><LF>.
   3. Issue <CR><LF>.
   4. Wait for a line of response.
      If it contains HTTP/1.X 200 , the connection is successful.
   5. Read further lines of response until you receive an empty line.
   6. Now, you are connected to outside world through a proxy.
      Do any data exchange you want.

-- 
Matthias Urlichs   |   {M:U} IT Design @ m-u-it.de   |  smurf@smurf.noris.de
Disclaimer: The quote was selected randomly. Really. | http://smurf.noris.de
 - -
Almost all absurdity of conduct arises from the imitation of those who we
cannot resemble.
					-- Samuel Johnson

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  parent reply	other threads:[~2005-10-05 12:52 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-04 21:42 cvsimport using proxy? Junio C Hamano
     [not found] ` <46a038f90510050309t1d075d7fj37c60a6052ec62f3@mail.gmail.com>
2005-10-05 12:50   ` Matthias Urlichs [this message]
2005-10-05 13:55     ` Johannes Schindelin

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20051005125055.GF4682@kiste.smurf.noris.de \
    --to=smurf@smurf.noris.de \
    --cc=git@vger.kernel.org \
    --cc=junkio@cox.net \
    --cc=martin.langhoff@gmail.com \
    --cc=martin@ng.eduforge.org \
    --cc=skimo@kotnet.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox