Tetra-WebBBS Support Forum
: There is an .htaccess file on our website.
Seems you've found the place where the webserver is advised to cache.
: # Requires mod_expires to be enabled.
: <IfModule mod_expires.c>
: # Enable expirations.
: ExpiresActive On
: # Cache all files for 2 weeks after access (A).
: ExpiresDefault A1209600
: <FilesMatch \.php$>
: # Do not allow PHP scripts to be cached unless they explicitly send
: # headers themselves. Otherwise all scripts would have to overwrite
: # headers set by mod_expires if they want another caching behavior.
: This may
: # fail if an error occurs early in the bootstrap process, and it
: may cause
: # problems if a non-Drupal PHP file is installed in a subdirectory.
: ExpiresActive Off
The part highlighted probably indicates the .htaccess entry is written by Drupal.
Great they take care of *.php scripts but don't care about other languages.
Unless there is anything else in the .htaccess file which is required to keep your server going, you may simply rename the file to ".htaccess_stopped" and see what happens.
Unfortunately Drupal will probably re-create the .htaccess file, but renaming may give enough time to do some tests.
Then you may check Drupal and disable it's caching "optimisation".
If you keep using Drupal, another option would be to place a second .htaccess file in all subdirectories which are not supposed to be managed by Drupal. The second .htaccess file may then overwrite the first one.
The following may do such a thing:
<IfModule mod_expires.c> ExpiresActive Off </IfModule>
Anyway, you're getting closer