Return-Path: Delivered-To: apmail-httpd-dev-archive@httpd.apache.org Received: (qmail 90827 invoked by uid 500); 13 Jun 2002 10:58:27 -0000 Mailing-List: contact dev-help@httpd.apache.org; run by ezmlm Precedence: bulk Reply-To: dev@httpd.apache.org list-help: list-unsubscribe: list-post: Delivered-To: mailing list dev@httpd.apache.org Received: (qmail 90814 invoked from network); 13 Jun 2002 10:58:26 -0000 User-Agent: Microsoft-Entourage/10.0.0.1331 Date: Thu, 13 Jun 2002 11:56:59 +0100 Subject: Re: Status line problems... From: Pier Fumagalli To: Cc: Stefan Norberg Message-ID: In-Reply-To: <20020613033209.O22524@apache.org> Mime-version: 1.0 Content-type: text/plain; charset="US-ASCII" Content-transfer-encoding: 7bit X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N "Justin Erenkrantz" wrote: > On Thu, Jun 13, 2002 at 11:24:51AM +0100, Pier Fumagalli wrote: >> Folks, I don't really get this one... Maybe someone can enlighten me. Stefan >> is using mod_webapp on HP_UX, with Apache 1.3.23. >> >> WebApp sets the status line in the request_rec structure, doing something >> like: >> >> if (status !=NULL && status[0]!='\0') >> req->status_line=apr_pstrdup(req->pool,status); >> >> Now, it happens that when that line is in place, oddly enough, the response >> seen by the client instead of being >> >> HTTP/1.1 XXX My Message Goes Here >> >> comes out as >> >> HTTP/1.1 My Message Goes Here > > What is status (your string) in this case? It would be "My Message Goes Here".... > The status_line field should contain the code as well as the text > message. The r->status field isn't automatically prepended to > the status_line. -- justin Awwww FU*KME! :( I wasn't able to reproduce it because I wasn't setting the status line on darn Tomcat... Folks I _AM_ stupid... Justin, go to bed! :) Pier