Hi, Ivan, all,
Ivan M wrote:
Hi T.J., all,

I would guess it's caused by the caching issue - a cached page was
incorrectly being served to you -

As a long-time systems programmer, I quite agree . . .

 I have seen this happen on other
sites that use more aggressive caching. Additionally, the issue of odd
messages appearing for users who had nothing to do with them (password
reset messages) have been reported in the last few months. Please vote
for issue 94328 as well:
http://qa.openoffice.org/issues/show_bug.cgi?id=94328 ... maybe
something can finally be done about this.

Regards,
Ivan.

@Ivan,
Thanks for the link. It saved me the trouble of preparing to file the issue myself, and then finding this one while searching for prior art. Notice that I was dealing with the 94328 problem (by pressing Ctrl+F5) when I hit the 99510 security-breach bug.

On Mon, Feb 23, 2009 at 6:54 AM, T. J. Frazier <[email protected]> wrote:
John McCreesh wrote:
Something similar was reported and investigated a couple of years ago.
http://www.openoffice.org/issues/show_bug.cgi?id=74642
Could you please re-open this issue, or open a new one referring to 74642?

Thanks - John
Thanks, John. I haven't the perks to re-open an issue, so I filed
http://www.openoffice.org/issues/show_bug.cgi?id=99510
and sent a comment on 74642.

Per 74642, I have installed Live-headers extension, and will try to
reproduce.

@all,
If anybody can tell me more about the Live-headers extension, especially what to do if I do manage to reproduce a bug, I would appreciate it. AFAIK, I have to run with it in an open tab, to capture anything, so that's what I'm doing. It looks like, in the event of a bug hit, I should save the header page and the generator page, and attach those files to a bug report.

If I hit the login bug, would it be of any use for me to capture the page source (View source, copy&paste to Notepad)?

Thanks, /tj/

--
T. J. Frazier
Melbourne, FL

(TJFrazier on OO.o)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to