Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • Tor Tor
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 328
    • Issues 328
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 31
    • Merge requests 31
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • The Tor Project
  • Core
  • TorTor
  • Issues
  • #1859
Closed
Open
Issue created Aug 22, 2010 by Robert Hogan@hoganrobert

Using 'mytorexitnode.exit' request when mytorexitnode is both exit and client

Yesterday I ran an exit node called 'testnoderh' on my Tor instance and then sent a HTTP request through the same tor instance for 'www.google.com.testnoderh.exit'.

Tor didn't like that one bit. It built dozens of circuits very quickly and got nowhere with the request.

The debug log is 120MB unzipped, 2Mb zipped.

It's stored at: http://roberthogan.net/stuff/tor-goes-nuts.tar.bz2

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