The following reply was made to PR config/1235; it has been noted by GNATS.
From: Marc Slemko <[EMAIL PROTECTED]> To: "Srilekha Mudumbai [ITG]" <[EMAIL PROTECTED]> Cc: Apache bugs database <[EMAIL PROTECTED]> Subject: Re: config/1235: LOCATION directive in config Date: Wed, 15 Oct 1997 20:41:10 -0600 (MDT) On Wed, 15 Oct 1997, Srilekha Mudumbai [ITG] wrote: > > HI > > Thanks a lot for your reply. > > Actually I submitted this bug in the database. > There I have mentioned in detail everything No you didn't. Please read what I wrote. > > I am using Apache 1.2 1.2.what? 1.2.0? 1.2.1? 1.2.2? 1.2.4? > > According to this version, location directive is supported., > The problem arises when The Location directive has nothing to do with this. As described in the docs, it does something completely different. > > I try to do https://server:port/~person > as opposed to https://server:port/~person/ -- note the missing > back slash I know what you wrote. > > If I try the first one, then it goes to > table_set(..., "Location", construct_url(...)) under > handle_dir in mod_dir.c > > Now this gives a code 301 for HTTP_MOVED_PERMANENT > which is returned to the calling function which invariably > leads to server error instead of going to a function > that deals with this directive > > I am sure that there would be some patch available to fix > this or some suggestions should be available <sigh> It isn't like everyone in the world has this same problem. It works fine for me. Again, the Location directive has nothing to do with the Location header. > > The error in the log file would be > > say if I have some syntax "xyz" mentioned in .htaccess > it would say "xyz is not a valid command name" > which doesn;t happen if I include a back slash. What? That doesn't exactly make sense. Please post the _exact_ error. > > please give me suggestions. I am really struggling with this > problem > As I said before, does it happen if you don't use SSL? If you use Apache without the external SSL patch that you are using, do you get the same problem? If you don't, then it is something in the SSL patch you are using that is the problem. We can't support every patch to Apache. I am trying to help you figure out where the problem is, but you have to do as I ask.
