Return-Path: Delivered-To: new-httpd-archive@hyperreal.org Received: (qmail 28002 invoked by uid 6000); 22 Dec 1998 23:46:02 -0000 Received: (qmail 27994 invoked from network); 22 Dec 1998 23:46:00 -0000 Received: from smtp13.bellglobal.com (204.101.251.52) by taz.hyperreal.org with SMTP; 22 Dec 1998 23:46:00 -0000 Received: from mrelay ([192.168.1.119]) by smtp13.bellglobal.com (8.8.5/8.8.5) with ESMTP id SAA04760 for ; Tue, 22 Dec 1998 18:45:59 -0500 (EST) Received: from collective.lerdorf.on.ca by mrelay.bellglobal.com (PMDF V5.1-12 #26722) with ESMTP id <0F4E0094S4LSSU@mrelay.bellglobal.com> for new-httpd@apache.org; Tue, 22 Dec 1998 18:44:17 -0500 (EST) Date: Tue, 22 Dec 1998 18:45:47 -0500 (Eastern Standard Time) From: Rasmus Lerdorf Subject: Re: general/2615: Set-Cookie not sent with Redirect response In-reply-to: To: new-httpd@apache.org Message-id: MIME-version: 1.0 Content-type: TEXT/PLAIN; charset=US-ASCII X-X-Sender: rasmus@imap3.bellglobal.com Sender: new-httpd-owner@apache.org Precedence: bulk Reply-To: new-httpd@apache.org > IMHO, the ability to do so with Apache is quite useful. Would this > constitute a bug or a feature the developers chose not to implement? I > never gave it much thought until I had a specific need to set cookies with > redirects. I could think of a few instances where it would be useful with > other responses as well. Well, it isn't really Apache stopping you from doing this. I can do it just fine. Turn on your cookie warning thing and point your browser at: http://www.lerdorf.on.ca/cr.html For an example. -Rasmus