+1834. [func] fdupont
+ Added two new callouts (hook points) in the control agent.
+ The "auth" callout is executed after the basic authentication
+ (if configured) and the command processing. The "response"
+ callout is executed after the command processing and before
+ the HTTP response is returned.
+ (Gitlab #1421)
+
1833. [doc] sgoldlust
Many documentation corrections.
(Gitlab #1539)
reference and for callout contexts. The "response" argument is the
response which will be sent back to the resquesting client. It is
called after command processing. The next step status is ignored:
- the response eventually modified will be sent back.
+ the response possibly modified will be sent back.
*/
\ No newline at end of file
setBasicContext(request_);
// Body: "list-commands" is natively supported by the command manager.
+ // We add a random value in the extra entry: see next unit test
+ // for an explanation about how it is used.
auto r32 = isc::cryptolink::random(4);
ASSERT_EQ(4, r32.size());
int extra = r32[0];
setBasicContext(request_);
// Body: "list-commands" is natively supported by the command manager.
+ // We add a random value in the extra entry:
+ // - this proves that the auth callout can get the request argument
+ // - this proves that the auth callout can modify the request argument
+ // before the request is executed (the extra entry if still present
+ // would make the command to be rejected as malformed)
+ // - this proves that a value can be communicate between the auth
+ // and response callout points
+ // - this proves that the response callout can get the response argument
+ // - this proves that the response callout can modify the response
+ // argument
auto r32 = isc::cryptolink::random(4);
ASSERT_EQ(4, r32.size());
int extra = r32[0];