imagemap usage on CP servers

[Date Index]
[Thread Index]

[Date Prev]

[Date Next]

[Thread Prev]

[Thread Next]
bullet

imagemap usage on CP servers
bullet

To: not-park@park.org
Subject: imagemap usage on CP servers
From: "Brad Burdick [UUcom]" <bburdick@radio.com>
Date: Fri, 19 Jan 1996 10:35:30 -0500 (EST)

we are running into potential problems with imagemap usage. following are what i think your servers can do with built-in imagemap support. if this is not correct, please let me know.

if all of the server support built-in imagemaps, i propose that we do not use the imagemap cgi program for imagemaps. the cgi script requires extra overhead in configuring config files usually. by just using the .map extension and taking advantage of the servers built-in support, we should make this much more portable with minimal configuration.

eg,

would become

this will require us to change all of our current imagemap declarations, but it is s simple search/replace operation.

the only caveat here is that ncsa does NOT work with map files in the document root directory. ie, /file.map will not work. just means we have to be careful where map files are placed...no problem.

these are the additions we have to our ncsa 1.5 srm.conf file:

AddType text/x-server-parsed-html .shtml AddType text/x-imagemap .map AddType application/x-httpd-cgi .cgi

adelaide:

your netscape server (i think) supports built-in imagemap usage. ie, it is configured to handle files ending in .map the same as ncsa 1.5+ does internally?

imperial, seoul:

apache 1.0.0 should support internal imagemap usage.

japan:

ncsa 1.5 does support internal image map usage.

this came up because the imperial host is complaining that our imagemap file is not in the config file.

thoughts?

-brad -- Brad Burdick bburdick@radio.com Internet Multicasting Service, NPB, Suite 1155, Washington, DC 20045 Under contract from UUcom, Inc.

bullet
[Date Prev] [Date Next] [Thread Prev] [Thread Next]
bullet