Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
gajim
gajim
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 209
    • Issues 209
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 21
    • Merge Requests 21
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
  • Operations
    • Operations
    • Incidents
    • Environments
  • Analytics
    • Analytics
    • CI / CD
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
  • gajim
  • gajimgajim
  • Issues
  • #1746

Closed
Open
Opened Mar 25, 2006 by anonymous@anonymous

HostTester vs proxy.jabber.cd.chalmers.se

I'm not using Gajim, so maybe this is working just fine; I'd just like to get clarification on this.

I noted on jdev that Gajim's HostTester causes errors in the ejabberd proxy65 implementation used at proxy.jabber.cd.chalmers.se. Gajim sends a SOCKS5 CONNECT command to the same address (sha1(NoneNoneNone)) each time. The proxy notices that this cookie has already been used, and immediately disconnects.

So my questions are:

  1. Does Gajim interpret this as that the proxy is working? I think it should, but as I read the code it seems it doesn't.
  2. Should the proxy give a more courteous error message?
Assignee
Assign to
0.4
Milestone
0.4 (Past due)
Assign milestone
Time tracking
None
Due date
None
Reference: gajim/gajim#1746