Skip to content

GitLab

  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • thg thg
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 837
    • Issues 837
    • List
    • Boards
    • Service Desk
    • Milestones
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • mercurial
  • TortoiseHg
  • thgthg
  • Issues
  • #2094

Closed
Open
Created Aug 22, 2012 by Bitbucket Importer@bitbucket_importerOwner

proxy server setting ineffect for tortoisehg

Created originally on Bitbucket by illidan.modeler

The issue reported below are true for TortoiseHG 2.1.1 and 2.3.1.

I don't have a direct Intent connection and I have to use a proxy. I set the proxy server in 'global settings' for my tortoisehg in Windows. And I verfied that the resulted mercurial.ini was correct according to the Mercurial user manual.

I run hg in a DOS window. It claimed that it was using the proxy (as indicated on the 3rd line). Finally it got an error of 'abort: error:'.

{{{ hg --debug clone https://illidan_the_modeler:******@bitbucket.org/illidan_the_modeler/sudoku using https://bitbucket.org/illidan_the_modeler/sudoku proxying through http://172.19.6.47:8080 http auth: user illidan_the_modeler, password ****** sending capabilities command }}}

When I tries the same thing with tortoisehg GUI, I carefully checked that the 'Use proxy server' option was enabled. The error info was: URLError: [Errno 10060] command returned code 255

Before I issue the hg command, I had started Wireshark to monitor the outgoing traffic. I found that the traffic was sent to the remote server directly, with the proxy ignored.

{{{ 438 10.054562 10.142.104.141 bitbucket.org TCP 3343 > 443 [SYN] Seq=0 Win=65535 Len=0 MSS=1460 SACK_PERM=1 850 13.016122 10.142.104.141 bitbucket.org TCP 3343 > 443 [SYN] Seq=0 Win=65535 Len=0 MSS=1460 SACK_PERM=1 1063 19.030209 10.142.104.141 bitbucket.org TCP 3343 > 443 [SYN] Seq=0 Win=65535 Len=0 MSS=1460 SACK_PERM=1 1705 31.059953 10.142.104.141 bitbucket.org TCP 3356 > 443 [SYN] Seq=0 Win=65535 Len=0 MSS=1460 SACK_PERM=1 }}}

So I wonder if there's an issue preventing the proxy setting to be effective for tortoisehg.

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking