Re: Currently known issues with 2.0.23 (very few! :)

[Doug MacEachern]

On Wed, 8 Aug 2001, Jerry Baker wrote:
...
> There are two crashes in serial fashion immediately as soon as the form
> is posted via mod_ssl. Here they are in the order they appear on the
> machine:

if you could post your test case (your client, whats posted from the
client, what handles the post data, etc.), i'll look at in the
morning.  i've just been testing with:

% perl -e 'print "x" x 12048' | POST https://127.0.0.1:8443/echo_post

using various random sizes against the test handler below.

static int echo_post_handler(request_rec *r)
{
    int rc;
    long nrd;
    char buff[BUFSIZ];

    if (strcmp(r->handler, "echo-post")) {
        return DECLINED;
    }
    if (r->method_number != M_POST) {
        return DECLINED;
    }

    if ((rc = ap_setup_client_block(r, REQUEST_CHUNKED_ERROR)) != OK) {
        ap_log_error(APLOG_MARK, APLOG_ERR|APLOG_NOERRNO, 0,
                     r->server,
                     "ap_setup_client_block failed: %d", rc);
        return 0;
    }

    if (!ap_should_client_block(r)) {
        return OK;
    }

    fprintf(stderr, "going to echo %d bytes\n", r->remaining);

    while ((nrd = ap_get_client_block(r, buff, sizeof(buff))) > 0) {
        fprintf(stderr, "read %d bytes (wanted %d, remaining=%d)\n",
                nrd, sizeof(buff), r->remaining);
        ap_rwrite(buff, nrd, r);
    }

    fprintf(stderr, "done reading, %d bytes remain\n", r->remaining);
    
    return OK;
}