mod_mime/1010: AddType's interaction with browser caches can be confusing

[Brian Slesinsky <bs...@wired.com>]

>Number:         1010
>Category:       mod_mime
>Synopsis:       AddType's interaction with browser caches can be confusing
>Confidential:   no
>Severity:       non-critical
>Priority:       medium
>Responsible:    apache (Apache HTTP Project)
>State:          open
>Class:          doc-bug
>Submitter-Id:   apache
>Arrival-Date:   Mon Aug 18 15:20:01 1997
>Originator:     bslesins@wired.com
>Organization:
apache
>Release:        1.2
>Environment:
Solaris
>Description:
If you use AddType to change the mime type associated with a file
and verify the change in your browser, the browser will not pick up
the new mime type even if it's restarted, because the last-modified
date hasn't changed on the file.  It's necessary to touch the file or
flush your browser cache to see the change.  This can be very confusing.
>How-To-Repeat:

>Fix:
Add a warning to the mod_mime docs.  Or, Apache could keep a history
of when each extension's mime type was changed and send a last-modified
date of at least that time for files with that extension.  But that's
probably more trouble than it's worth.
%0
>Audit-Trail:
>Unformatted: