Received: by taz.hyperreal.com (8.6.12/8.6.5) id HAA22984; Sat, 20 Apr 1996 07:55:40 -0700 Received: from krone.house.mil by taz.hyperreal.com (8.6.12/8.6.5) with ESMTP id HAA22977; Sat, 20 Apr 1996 07:55:35 -0700 From: rasmus@madhaus.utcs.utoronto.ca Received: from krone.house.mil (krone.house.mil [192.75.57.2]) by krone.house.mil (8.7.1/8.7.1) with SMTP id KAA05417 for ; Sat, 20 Apr 1996 10:56:07 -0400 Date: Sat, 20 Apr 1996 10:56:06 -0400 (EDT) Subject: API Question - External Redirect To: new-httpd@hyperreal.com Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII Sender: owner-new-httpd@apache.org Precedence: bulk Reply-To: new-httpd@hyperreal.com I am trying to get a module to generate an external redirect header. ie. a set of HTTP header lines which contain a "Location: URL" line. The obvious way given the framework of the API would be to do something like: table_set(req->headers_out,"Location",url); send_http_header(req); Now, this won't work because send_http_header() calls basic_http_header() which sends along a Content-type along with some other headers. The Location header is sent, but it is further down the list. Is there an RFC which discusses precedence of http headers? ie. how does the browser determine that the Location header should be ignored? Is it the presence of the Content-type header before it? If so, should send_http_header() not check for a Location header and send that first if it is present in the "headers_out" table? Or is there some other way to do an external redirect from a module short of the module doing all the work itself? -Rasmus