You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@httpd.apache.org by Randy Terbush <ra...@zyzzyva.com> on 1997/08/02 18:00:13 UTC
Re: Docs problems?
> At 11:56 AM 8/1/97 -0500, Randy Terbush wrote:
> >I've gotten 4 such reports this morning. Does someone here know
> >what might have changes? If not, I'll try to get some time to check
> >this later today.
> ...
> >The link to the search page from http://www.apache.org/docs is broken.
> >It points to http://www.apache.org/manual-index/docs which the server
> >can't find.
>
> I think there's a content-negotiation and MultiViews problem with the
> latest 1.3a2-dev. I updated last night and started seeing some funkiness
> related to when multiviews needs to make a choice between two files to send
> out. In this case, there is a "manual-index.cgi", a "manual-index.dat",
> and a "manual-index.dat.old". I fixed this for now by making the call to
> "manual-index.cgi" explicit, but we should look into this. On the other
> hand, it is really bad practice to have the data file and the CGI script
> share the same basename in the same directory, and ask the server to
> negotiate between them. Ken, could you fix this?
>
> Brian
I agree that it is bad form to name these the same. Learned that
long ago. However, I seem to have to tell users this on a frequent
basis, and I total understand the desire to give these the same
basename. I wonder if we should consider some priority for
Multiviews that would force it to look for files with extensions in
a specific order. cgi --> shtml --> html etc.? I think that we can
do that with a .var, but there should probably be a default
behavior.
Re: Docs problems?
Posted by Dean Gaudet <dg...@arctic.org>.
Well I didn't think the code would give files with extensions that it
doesn't know about a high priority. So the cgi should be taken ... unless
hyperreal knows about .dat. Or unless mod_mime_magic has typed the .dat
file ... :)
Dean
On Sat, 2 Aug 1997, Randy Terbush wrote:
> > At 11:56 AM 8/1/97 -0500, Randy Terbush wrote:
> > >I've gotten 4 such reports this morning. Does someone here know
> > >what might have changes? If not, I'll try to get some time to check
> > >this later today.
> > ...
> > >The link to the search page from http://www.apache.org/docs is broken.
> > >It points to http://www.apache.org/manual-index/docs which the server
> > >can't find.
> >
> > I think there's a content-negotiation and MultiViews problem with the
> > latest 1.3a2-dev. I updated last night and started seeing some funkiness
> > related to when multiviews needs to make a choice between two files to send
> > out. In this case, there is a "manual-index.cgi", a "manual-index.dat",
> > and a "manual-index.dat.old". I fixed this for now by making the call to
> > "manual-index.cgi" explicit, but we should look into this. On the other
> > hand, it is really bad practice to have the data file and the CGI script
> > share the same basename in the same directory, and ask the server to
> > negotiate between them. Ken, could you fix this?
> >
> > Brian
>
> I agree that it is bad form to name these the same. Learned that
> long ago. However, I seem to have to tell users this on a frequent
> basis, and I total understand the desire to give these the same
> basename. I wonder if we should consider some priority for
> Multiviews that would force it to look for files with extensions in
> a specific order. cgi --> shtml --> html etc.? I think that we can
> do that with a .var, but there should probably be a default
> behavior.
>
>
>
>
>
>