Помогите разобраться с сабжем (скомпилен можулем для nginx). Насколько я понял, он отказывается пропускать POST запросы при включенной опции SecResponseBodyAccess On.
Если же эту опцию отключить (установить в Off), всё работает. Пот логи из первого (удачного) и второго (неудачного) случая:
[4] Initialising transaction (txid AcAGAc@cAcAcccAcAcAcpcAc).
[5] Adding request cookie: name "JSESSIONID", value "1"
[4] Transaction context created (dcfg 19d0040).
[4] Starting phase REQUEST_HEADERS.
[4] Second phase starting (dcfg 19d0040).
[4] Input filter: Request body access not enabled.
[4] Starting phase REQUEST_BODY.
[4] Hook insert_filter: Adding output filter (r 1a2fcf8).
[9] Output filter: Receiving output (f 1a30f08, r 1a2fcf8).
[4] Starting phase RESPONSE_HEADERS.
[4] Output filter: Response body buffering is not enabled.
[9] Content Injection: Not enabled.
[4] Output filter: Completed receiving response body (non-buffering).
[4] Starting phase RESPONSE_BODY.
[4] Output filter: Output forwarding complete.
[9] Output filter: Sending input brigade directly.
[4] Initialising logging.
[4] Starting phase LOGGING.
[4] Recording persistent data took 0 microseconds.
[4] Audit log: Ignoring a non-relevant request.
[4] Initialising transaction (txid AHAcAcKDAcAcAEDrAoAcA2Ac).
[5] Adding request cookie: name "JSESSIONID", value "1"
[4] Transaction context created (dcfg 227d040).
[4] Starting phase REQUEST_HEADERS.
[4] Second phase starting (dcfg 227d040).
[4] Input filter: Request body access not enabled.
[4] Starting phase REQUEST_BODY.
[4] Hook insert_filter: Adding output filter (r 22dccf8).
[9] Output filter: Receiving output (f 22ddf08, r 22dccf8).
[4] Starting phase RESPONSE_HEADERS.
[4] Output filter: Not buffering response body for unconfigured MIME type "null".
[9] Content Injection: Not enabled.
[4] Output filter: Completed receiving response body (non-buffering).
[4] Starting phase RESPONSE_BODY.
[4] Output filter: Output forwarding complete.
[9] Output filter: Sending input brigade directly.