. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112 6.1.1 Usurpation de la chaîne User-Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113 6.1.2 Extension avec des exemples de commandes de l’interpréteur bash(1). # command-in-root-account $ command-in-user-account Référence Debian xxv Ces invites de l’interpréteur de commandes permettent de distinguer (C’ est UNIX. Il vous donne assez de corde pour vous pendre vous-même). — « UNIX IS user friendly... It’s just selective about who its friends are. » --- Tollef Fog Heen (UNIX

participant User User -> A: DoWork activate A A -> B: << createRequest >> activate B B -> C: DoWork activate C C --> B: WorkDone destroy C B --> A: RequestCreated deactivate B A -> User: Done deactivate lignes de vie peuvent être imbriquées, et il est possible de les colorer. @startuml participant User User -> A: DoWork activate A #FFBBBB A -> A: Internal call activate A #DarkSalmon A -> B: << createRequest PlantUML (1.2020.23) 17 / 307 1.23 Return 1 DIAGRAMME DE SÉQUENCE deactivate B deactivate A A -> User: Done deactivate A @enduml 1.23 Return A new command return for generating a return message with

participant User User -> A: DoWork activate A A -> B: << createRequest >> activate B B -> C: DoWork activate C C --> B: WorkDone destroy C B --> A: RequestCreated deactivate B A -> User: Done deactivate lignes de vie peuvent être imbriquées, et il est possible de les colorer. @startuml participant User User -> A: DoWork activate A #FFBBBB A -> A: Internal call activate A #DarkSalmon A -> B: << createRequest PlantUML (1.2020.22) 16 / 294 1.22 Return 1 DIAGRAMME DE SÉQUENCE deactivate B deactivate A A -> User: Done deactivate A @enduml 1.22 Return A new command return for generating a return message with

participant User User -> A: DoWork activate A A -> B: << createRequest >> activate B B -> C: DoWork activate C C --> B: WorkDone destroy C B --> A: RequestCreated deactivate B A -> User: Done deactivate lignes de vie peuvent être imbriquées, et il est possible de les colorer. @startuml participant User User -> A: DoWork activate A #FFBBBB A -> A: Internal call activate A #DarkSalmon A -> B: << createRequest PlantUML (1.2019.6) 15 / 173 1.20 Return 1 DIAGRAMME DE SÉQUENCE deactivate B deactivate A A -> User: Done deactivate A @enduml 1.20 Return A new command return for generating a return message with

participant User User -> A: DoWork activate A A -> B: << createRequest >> activate B B -> C: DoWork activate C C --> B: WorkDone destroy C B --> A: RequestCreated deactivate B A -> User: Done deactivate lignes de vie peuvent être imbriquées, et il est possible de les colorer. @startuml participant User User -> A: DoWork activate A #FFBBBB A -> A: Internal call activate A #DarkSalmon A -> B: << createRequest PlantUML (1.2019.9) 15 / 173 1.20 Return 1 DIAGRAMME DE SÉQUENCE deactivate B deactivate A A -> User: Done deactivate A @enduml 1.20 Return A new command return for generating a return message with

participant User User -> A: DoWork activate A A -> B: << createRequest >> activate B B -> C: DoWork activate C C --> B: WorkDone destroy C B --> A: RequestCreated deactivate B A -> User: Done deactivate lignes de vie peuvent être imbriquées, et il est possible de les colorer. @startuml participant User User -> A: DoWork activate A #FFBBBB A -> A: Internal call activate A #DarkSalmon A -> B: << createRequest PlantUML (1.2019.4) 15 / 167 1.20 Return 1 DIAGRAMME DE SÉQUENCE deactivate B deactivate A A -> User: Done deactivate A @enduml 1.20 Return A new command return for generating a return message with

participant User User -> A: DoWork activate A A -> B: << createRequest >> activate B B -> C: DoWork activate C C --> B: WorkDone destroy C B --> A: RequestCreated deactivate B A -> User: Done deactivate lignes de vie peuvent être imbriquées, et il est possible de les colorer. @startuml participant User User -> A: DoWork activate A #FFBBBB A -> A: Internal call activate A #DarkSalmon A -> B: << createRequest PlantUML (1.2019.3) 15 / 159 1.20 Return 1 DIAGRAMME DE SÉQUENCE deactivate B deactivate A A -> User: Done deactivate A @enduml 1.20 Return A new command return for generating a return message with

participant User User -> A: DoWork activate A A -> B: << createRequest >> activate B B -> C: DoWork activate C C --> B: WorkDone destroy C B --> A: RequestCreated deactivate B A -> User: Done deactivate lignes de vie peuvent être imbriquées, et il est possible de les colorer. @startuml participant User User -> A: DoWork activate A #FFBBBB A -> A: Internal call activate A #DarkSalmon A -> B: << createRequest PlantUML (1.2019.2) 15 / 159 1.20 Return 1 DIAGRAMME DE SÉQUENCE deactivate B deactivate A A -> User: Done deactivate A @enduml 1.20 Return A new command return for generating a return message with

participant User User -> A: DoWork activate A A -> B: << createRequest >> activate B B -> C: DoWork activate C C --> B: WorkDone destroy C B --> A: RequestCreated deactivate B A -> User: Done deactivate participant User User -> A: DoWork activate A #FFBBBB A -> A: Internal call activate A #DarkSalmon A -> B: << createRequest >> activate B B --> A: RequestCreated deactivate B deactivate A A -> User: Done 60 skinparam sequenceParticipant underline actor User participant "First Class" as A participant "Second Class" as B participant "Last Class" as C User -> A: DoWork activate A A -> B: Create Request activate

practices with minimal setup. If you are familiar with Flask, Flask-RESTful should be easy to pick up. User’s Guide This part of the documentation will show you how to get started in using Flask- RESTful with DELETE a task $ curl http://localhost:5000/todos/todo2 -X DELETE -v > DELETE /todos/todo2 HTTP/1.1 > User-Agent: curl/7.19.7 (universal-apple-darwin10.0) libcurl/7.19.7 OpenSSL/0.9.8l zlib/1.2.3 > Host: task $ curl http://localhost:5000/todos -d "task=something new" -X POST -v > POST /todos HTTP/1.1 > User-Agent: curl/7.19.7 (universal-apple-darwin10.0) libcurl/7.19.7 OpenSSL/0.9.8l zlib/1.2.3 > Host: