Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • Trac Trac
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Issues 246
    • Issues 246
    • List
    • Boards
    • Service Desk
    • Milestones
  • Monitor
    • Monitor
    • Metrics
    • Incidents
  • Analytics
    • Analytics
    • Value stream
  • Wiki
    • Wiki
  • Activity
  • Create a new issue
  • Issue Boards
Collapse sidebar
  • Legacy
  • TracTrac
  • Issues
  • #6667

Closed (moved)
(moved)
Open
Created Aug 23, 2012 by neena@neena

SETCIRCUITPURPOSE's format in the control spec is misleading

From the control spec...

 761 3.11. SETCIRCUITPURPOSE
 762 
 763   Sent from the client to the server.  The format is:
 764       "SETCIRCUITPURPOSE" SP CircuitID SP Purpose CRLF
 765 
 766   This changes the circuit's purpose. See EXTENDCIRCUIT above for details.

And from 'EXTENDCIRCUIT above'...

3.10. EXTENDCIRCUIT
 736 
 737   Sent from the client to the server.  The format is:
 738       "EXTENDCIRCUIT" SP CircuitID
 739                       [SP ServerSpec *("," ServerSpec)]
 740                       [SP "purpose=" Purpose] CRLF

This seems to imply that "SETCIRCUITPURPOSE 4 controller" is valid, but, it isn't, "SETCIRCUITPURPOSE 4 purpose=controller" is.

 764       "SETCIRCUITPURPOSE" SP CircuitID SP Purpose CRLF

should be...

 764       "SETCIRCUITPURPOSE" SP CircuitID SP "purpose=" Purpose CRLF

I'm attaching a git formatted patch which makes this modification.

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