I am having an interesting experience with an unkillable
cache. This is the environment. Running RH 8.0 mostly
out of the box.
2.4.18-14smp #1 SMP Wed Sep 4 12:34:47 EDT 2002 i686 i686 i386 GNU/Linux
Apache/1.3.19 ColdfusionMX, PHP 4.2.2
What is happening is that one of the users is connecting
to the development web server through Samba. He places
cold fusion files in the dir. Then he reloads the page
to see his changes. Sometimes he doesn't. When he told
me this I told him to flush the cache on his browser.
He demonstrated something I STILL can't figure out. Hoping
one of you can because it is a real problem.
First he showed me a cold fusion file in browsers on
several machines. No possible way it is a browser cache.
I verified that the file did not exist on the hard drive.
So not a SAMBA problem. I created a file by the same name
and instead of the ghost file being executed the newly
named file was. Deleted the file we shall call xyz.cfm
for this email and the ghost file reappeared!
I brought down the coldfusion and httpd services. Brought
them back up. Ghost file still there. Turned off caching
in Coldfusion. Verified that caching was still remarked
out in the httpd.conf file. Restarted both. File still
there. Cold booted the server. Viewed ghost file from a
machine that as far as we know never ever viewed this
file before. It was STILL there???
I am not doing any disk caching or anything fancy with
the file system. We eventually found that the ghost
file disapeared. I belive after I applied the latest
patches to Coldfusion. It has remanifested itself with
other files however. It is driving the developers nutts.
Anybody have any ideas?
Loaded modules
mod_jrun, mod_put, mod_ssl, mod_dav, mod_php4, mod_perl, mod_setenvif, mod_so, mod_headers, mod_expires, mod_auth_db, mod_auth_anon, mod_auth, mod_access, mod_rewrite, mod_alias, mod_userdir, mod_actions, mod_imap, mod_asis, mod_cgi, mod_dir, mod_autoindex, mod_include, mod_info, mod_status, mod_negotiation, mod_mime, mod_log_referer, mod_log_agent, mod_log_config, mod_env, mod_throttle, mod_bandwidth, mod_vhost_alias, http_core
cache. This is the environment. Running RH 8.0 mostly
out of the box.
2.4.18-14smp #1 SMP Wed Sep 4 12:34:47 EDT 2002 i686 i686 i386 GNU/Linux
Apache/1.3.19 ColdfusionMX, PHP 4.2.2
What is happening is that one of the users is connecting
to the development web server through Samba. He places
cold fusion files in the dir. Then he reloads the page
to see his changes. Sometimes he doesn't. When he told
me this I told him to flush the cache on his browser.
He demonstrated something I STILL can't figure out. Hoping
one of you can because it is a real problem.
First he showed me a cold fusion file in browsers on
several machines. No possible way it is a browser cache.
I verified that the file did not exist on the hard drive.
So not a SAMBA problem. I created a file by the same name
and instead of the ghost file being executed the newly
named file was. Deleted the file we shall call xyz.cfm
for this email and the ghost file reappeared!
I brought down the coldfusion and httpd services. Brought
them back up. Ghost file still there. Turned off caching
in Coldfusion. Verified that caching was still remarked
out in the httpd.conf file. Restarted both. File still
there. Cold booted the server. Viewed ghost file from a
machine that as far as we know never ever viewed this
file before. It was STILL there???
I am not doing any disk caching or anything fancy with
the file system. We eventually found that the ghost
file disapeared. I belive after I applied the latest
patches to Coldfusion. It has remanifested itself with
other files however. It is driving the developers nutts.
Anybody have any ideas?
Loaded modules
mod_jrun, mod_put, mod_ssl, mod_dav, mod_php4, mod_perl, mod_setenvif, mod_so, mod_headers, mod_expires, mod_auth_db, mod_auth_anon, mod_auth, mod_access, mod_rewrite, mod_alias, mod_userdir, mod_actions, mod_imap, mod_asis, mod_cgi, mod_dir, mod_autoindex, mod_include, mod_info, mod_status, mod_negotiation, mod_mime, mod_log_referer, mod_log_agent, mod_log_config, mod_env, mod_throttle, mod_bandwidth, mod_vhost_alias, http_core