Databases
StackOverflow2013
Postsdbo
POGit Bash on windows 7 behind proxy no longer working
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POGit Bash on windows 7 behind proxy no longer working
    primarykey
    data
    text
    <p>I'm on a windows 7, 32 bit box, and working behind a proxy. I just upgraded my git client (Git Bash) to <code>Git-1.8.3-preview20130601</code>, and all of the sudden, I'm getting the following error whenever I try to push/pull:</p> <pre><code>fatal: unable to access 'https://github.com/User/simple_timesheets.git/: Received HTTP code 407 from proxy after Connect </code></pre> <p>I was able to do this just fine before upgrading, and even when I tried to revert back to the last version that I think I had, I still get the error. When I run <code>git config -l</code>, it lists out the following variables (among others):</p> <pre><code>user.name=MyName user.email=My@email.com http.proxy=http://user:password@server:port core.autocrlf=true https.proxy=http://user:password@server:port http.sslcainfo=/bin/curl-ca-bundle.crt </code></pre> <p>What's odd is that I seem to be able to use the <code>Git Bash</code> client to curl just fine</p> <pre><code>curl finance.yahoo.com --proxy http://user:password@server:port </code></pre> <p>and can even curl into a dummy https site I set up on my computer:</p> <pre><code>curl https://localhost:3000 --insecure </code></pre> <p>Any ideas what I'm missing? Thanks</p> <hr> <p>EDIT:</p> <p>I could be wrong, but I think there might be an issue with curl in version 1.8.3. I uninstalled all git related applications I could think of on my computer, and installed <code>Git-1.8.0-preview20121022</code>, ran a pull on a repo and was successful.</p> <p>For giggles, I uninstalled the working version, and kept the cert file; then reinstalled version 1.8.3 to see if this didn't have anything to do with it, but I got the same error I was originally trying to resolve.</p> <p>Also, after re-installing version 1.8.0, I tried to curl an https website (gmail), with the following command: <code>curl https://www.gmail.com --proxy http://user:pass@server:port</code>, which was successful. When I did this under 1.8.3, I got an error about code 407. The version switch seems like it solved this.</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PTQuestion
    1. USJWally
    1. USJWally
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. POGit Bash on windows 7 behind proxy no longer working
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POGit Bash on windows 7 behind proxy no longer working
      1. USnulltoken
      1. VTFavorite
    3. VO
      singulars
      1. POGit Bash on windows 7 behind proxy no longer working
      1. This table or related slice is empty.
      1. VTUpMod
    1. COI just tried running the following: `curl https://www.gmail.com --proxy http://user:password@server:port > gmail.html`, and it gave the following: `curl: (56) Received HTTP code 407 from proxy after CONNECT`
      singulars
      1. POGit Bash on windows 7 behind proxy no longer working
      1. USJWally
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload