Re: Assigned paths

• Messages sorted by: [ date ][ thread ][ subject ][ author ]
• Next message: Hallam-Baker: "Re: Assigned paths"
• Previous message: David W. Morris: "Proposal: 100-Continue optional under Client control"
• Maybe in reply to: Ross Patterson: "Assigned paths"
• Next in thread: Hallam-Baker: "Re: Assigned paths"
• Reply: Hallam-Baker: "Re: Assigned paths"

Graham Klyne writes:
> Referring to the CGI example from your earlier posting: "/cgi-bin/..."
> isn't it whatever lies at the end of the "..." bit (i.e. something the
> server recognizes as a CGI script) which triggers the server into CGI
> invocation, rather than the "/cgi-bin" prefix?

Either a prefix like /cgi-bin or suffix like .cgi may be relevant, depending
on the server config.

Apache uses a ScriptAlias directive to inform the server that the directory
referenced by /cgi-bin contains executable files rather than documents.  In
that sense, it is the /cgi-bin prefix which triggers the server.  However,
you can configure Apache to recognize scripts stored in other directories by
declaring a handler for a particular file extension, and in that case it is
the .cgi suffix which triggers the server.

--Jeff

• Next message: Hallam-Baker: "Re: Assigned paths"
• Previous message: David W. Morris: "Proposal: 100-Continue optional under Client control"
• Maybe in reply to: Ross Patterson: "Assigned paths"
• Next in thread: Hallam-Baker: "Re: Assigned paths"
• Reply: Hallam-Baker: "Re: Assigned paths"