Philip M. Gollucci wrote:
> Just for kicks, can you try it in another browser like FireFox ?
A logical suggestion, but:
1. IE with default security and privacy settings is my target browser.
If IE has an issue with internal_redirect(), I need to deal with it
at the mod_perl end.
2. I have an aversion to installing software on Windows machines --
the only way to truly get the machine back to the state it was in
prior to installing the software is to take a Ghost image first,
install the software, and then do a Ghost restore. The catch-22 is
when you install the software, think it's okay, run the box for
[hours|days|weeks|months], make system changes along the way, and
then realize that the software must be removed. Restoring the
Ghost image means backing up your data first, doing the Ghost
restore (losing all those changes you made after installing the
software), re-doing all those changes, and restoring you data. Not
restoring means being stuck with any non-uninstallable portions of
the software and/or any side-effects or artifacts of installing or
running the software.
I'm wondering if anybody out there has seen this symptom, knows the explanation
why, and can point me towards a good solution. An Eagle book page reference,
man page reference, perldoc reference, URL, etc. is all I'm looking for.
Some work-arounds come to mind:
1. Make a mod_perl call that tells the browser not to cache the
upcoming document. (Does such a call exist?)
2. Make a mod_perl call that tells the browser that the upcoming
document is newer than the last one requested (I might be able to
implement this idea using time(), update_mtime(), and
set_last_modified(), but it seems like a crude hack).
David
