Re: protocol/1399: MISE 4.0 POST, then 401 Unauth, then second POST with good uname/pwd, garbage data in logs and (sometimes) garbled request

[In order for any reply to be added to the PR database, ] [you need to include [EMAIL PROTECTED] in the Cc line ] [and leave the subject line UNCHANGED. This is not done] [automatically because of the potential for mail loops. ] Synopsis: MISE 4.0 POST, then 401 Unauth, then second POST with

mod_imap/1734: SIGSEGV in mod_imap.c

Number: 1734 Category: mod_imap Synopsis: SIGSEGV in mod_imap.c Confidential: no Severity: non-critical Priority: medium Responsible:apache State: open Class: sw-bug Submitter-Id: apache Arrival-Date: Tue Jan 27 05:50:01 PST 1998

Re: mod_imap/1734: SIGSEGV in mod_imap.c

Synopsis: SIGSEGV in mod_imap.c State-Changed-From-To: open-analyzed State-Changed-By: marc State-Changed-When: Tue Jan 27 06:39:33 PST 1998 State-Changed-Why: Erm... why do you think the third argument is supposed to be q request_rec? mod_imap.c: return construct_url(r-pool, r-uri,

Re: mod_imap/1734: SIGSEGV in mod_imap.c

On 27 Jan 1998 [EMAIL PROTECTED] wrote: Synopsis: SIGSEGV in mod_imap.c State-Changed-From-To: open-analyzed State-Changed-By: marc State-Changed-When: Tue Jan 27 06:39:33 PST 1998 State-Changed-Why: Erm... why do you think the third argument is supposed to be q request_rec?