-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 All, I'm looking at moving from mod_jk to mod_proxy and I need to migrate my tooling for things like scripted worker-management. My existing tool for mod_jk is on GitHub[1] for those interested in what it can do. Mostly, I'm interested in fetching and setting the status(es) of a worker. With mod_jk, status is one of Active, Disabled, Stopped. The difference between Disabled and Stopped is that requests for sticky-sessions pointing to a Disabled will still be routed to the Disabled worker while a Stopped worker will never receive a request. By looking at a little of the mod_proxy_balancer code and poking at the interface a little bit, I have drawn these conclusions. Can anyone confirm that they are accurate? 1. Nonce is required for many operations (but not status-fetch?) 2. Nonce is only available once an initial GET has completed succesfully ... by sniffing the nonce from an href URL 3. You can get XML details for the balancers ... but only with a nonce and an "xml" parameter 4. You can change any individual flag, eg. "draining", by making a POST request which includes a w_status_[F]=0|1 parameter where [F] is one of several flag characters (e.g. N for "draiNing") along with a "b" (balancer) and "w" (worker) parameter. Unspecified flags and other settings will be unaffected. The nonce is required for these operations. 5. The "draiN" status of mod_proxy_balancer workers is analagous to the "disabled" status of mod_jk, and both "Disabled" and "Stopped" in mod_proxy are roughly equivalent to "Disabled" state for mod_jk. Does all that sound right? Would it be possible to query the status with XML-output *without* a nonce? And could the nonce be added to the XML output? Thanks, - -chris [1] https://github.com/ChristopherSchultz/apache-tomcat-stuff/tree/master/bi n/mod_jk -----BEGIN PGP SIGNATURE----- Comment: Using GnuPG with Thunderbird - https://www.enigmail.net/ iQIzBAEBCAAdFiEEMmKgYcQvxMe7tcJcHPApP6U8pFgFAl8DsxoACgkQHPApP6U8 pFiCiA//Yos4iP5FxpgMxW9FFtH+B0eDWkyoZiBbWzSnfLVwrF11Y1nnJHRDashH RZxiqosqnce6g6CeSzIpCyNFoAVLXGc1MKgoS+kOBkw83KW+JMKVh4AhlLxu0PdT zaG+uSvBNIIkJUivjyStOltCvNOHJnD7Q1Wj51GCSGFX75rMXK9aZfHu/ChxyRgT AISFdiAzBKnZvkf1f3WRXJPgc0JRB+Vf3cq0c1jKKdAy6hMX/g0UdJZ05JH7NwcF LPdwov/13rJMlrwxG/VegCsNaFQhh+v+uZ7mxNex/eoljzFVL6QTkOJoknFaDZBL 87+gavBbLqt4etmzp8VcJoQNW7Ol2PsRy95Mhscq/qHrwFKyqy5UP+XLU5q1No8N qojoh63GOX47p7t1S1XF8SeOzbWLy2kPVnZD67/mPOJVtDMd5IJTQ0/TeSME9Q8p n/zOjKQy+elRhZm5UMPOo2tm8iV8FlmMMnZ9JOlW1mDXAwRSdb5qQQ2i8Qpdlmq7 JWW4MrNoJJOz2JXMbkbp/yQCd2naU170oZsj0HgSjTuit6YjGGcjwlz009B+n8na npWHZVWCqiSHr66cfQqeCpW/T7i/V0olp1huzMovgC9ipkUiWu2ZvCq8rgAIP0fz hYAg4nBikS1dWPN3FEImgrysMPvrHQLx+/1i458G0QBwCun/r5k= =AfYi -----END PGP SIGNATURE----- --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscribe@xxxxxxxxxxxxxxxx For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx
|