public inbox for
help / color / mirror / Atom feed
Subject: gnatsweb/408: submit error with debug=all
Date: Tue, 13 Aug 2002 10:59:00 -0000	[thread overview]
Message-ID: <> (raw)

>Number:         408
>Category:       gnatsweb
>Synopsis:       submit error with debug=all
>Confidential:   no
>Severity:       serious
>Priority:       high
>Responsible:    unassigned
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Tue Aug 13 13:58:59 -0400 2002
>Originator:     Anders Johnson
>Release:        3.99.3/1.93 w/Gerald's 8/10/02 debugging patch
WIS Technologies
Submitting an edit (or new PR) with debug=all causes a web server error. (See "How-To-Repeat".) However, the database reflects the change as if there were no problem.
[This is preventing me from chasing down another problem that occurs only on submit edit.]
If I edit a PR, then insert "&debug=all" between "&database=default" and "&pr=1" in the URL and reload, then I get the debug info as expected, and everything is OK. However, if I then submit a change to the PR, I get:
    Internal Server Error
    The server encountered an internal error or misconfiguration and was
unable to complete your request.
    Please contact the server administrator, root@localhost and inform them of the time the error occurred, and anything you might have done that may have caused the error.
    More information about this error may be available in the server error log.

The apache log then includes:
    [Mon Aug 12 12:08:10 2002] [error] [client] malformed header from script. Bad header=</tt><br>: /var/www/cgi-bin/

Gnats-prs mailing list

                 reply	other threads:[~2002-08-13 17:59 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).