Well, at first I really didn't think that was it. But I wanted to be sure, so I started doing some research on IE and it's caching of POST data. Apparently it does cache the post data if you utilize get data as well. In other words:
<form action="/form.xsp?stuff=whatever" method="post" /> I'm not doing that, but I still wasn't comfortable. So I began utilizing the 'cache-control: no-cache' header, as documented via http://support.microsoft.com/default.aspx?scid=KB;EN-US;Q234067&;. That didn't solve it, so I hit it with Netscape 7. Still no results. Netscape 7 has a nifty feature of 'View->Page Info'. In this dialog it says explicitly, "Source: (not cached)". So I know that it's not caching the page source. But I don't think it's caching the post data either. I've taken all the steps I know of to eliminate that possibility, and AFAIK browsers don't really cache that data, because it's obvious that you wouldn't want to always resubmit the same info to a form. IE explicitly asks you if you want to resubmit the same data. Additionally, my entries into the field would override any POST cache. Wouldn't it? ----- Original Message ----- From: "Tod Harter" <[EMAIL PROTECTED]> To: "Riley James" <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]> Sent: Tuesday, October 01, 2002 4:55 AM Subject: Re: PerForm *too* sticky > On Monday 30 September 2002 11:09 pm, Riley James wrote: > > It HAS to be a browser cache problem IMHO. > > I can think of many ways it could happen, but all of them involve some sort > of misconfigured or malfunctioning software. I'd start out by testing with a > client that does no caching and is running either on or very close to the box > serving the pages. That eliminates most variables. > > From there I'd test from other locations and with other client applications > and try to isolate it down to one specific element in the equation. Then you > can figure out what the fix is. > > > > > I must assume that either I'm doing something so stupid and obvious that no > > one can believe it, or that no one else has any answers to this. Either is > > fine, I just need to know which one... > > > > > > ----- Original Message ----- > > From: "Riley James" <[EMAIL PROTECTED]> > > To: <[EMAIL PROTECTED]> > > Sent: Tuesday, September 24, 2002 12:36 PM > > Subject: Re: PerForm *too* sticky > > > > > I call /stylesheets/general.xsl which <xsl:include>'s perform_html.xsl. > > > I am using the perform_html.xsl that comes with PerForm but with slight > > > modification. I've added 2 attributes to the PerForm tags, tdlabel and > > > calendar. Since I couldn't wrap the perform tags in a table in the XSP, > > > > and > > > > > adding the table in XSL didn't allow me to know the display name of each > > > field, I've got tdlabel. This turns: > > > > > > <f:textfield name="test" tdlabel="This is a test" /> > > > > > > into > > > <tr> > > > <th>This is a test: </th> > > > <td><input type="text" name="test"></td> > > > </tr> > > > > > > And the entire thing is always wrapped in a uniform table. This suits my > > > needs for the type of intranet site I'm building. > > > > > > The calendar attribute is applied only to textfield's and simply tells > > > the stylesheet to tie a javascript popup calendar to that textfield. I've > > > attached the perform_html.xsl stylesheet. > > > > > > ----- Original Message ----- > > > From: "Matt Sergeant" <[EMAIL PROTECTED]> > > > To: "Riley James" <[EMAIL PROTECTED]> > > > Cc: <[EMAIL PROTECTED]> > > > Sent: Monday, September 23, 2002 12:36 PM > > > Subject: Re: PerForm *too* sticky > > > > > > > On Monday, Sep 23, 2002, at 17:06 Europe/London, Riley James wrote: > > > > > I've been experiencing an issue where PerForm seems to be > > > > > hyper-sticky, reprocessing the same form parameters over and over > > > > > even though they're being entered differently. > > > > > > > > > > This is happening inconsistently (it'll work long enough to make me > > > > > think it's not a problem, then I come back in a couple hours). > > > > > > > > > > For instance, I have an XSP page which is a very simple search. The > > > > > form posts to itself, and I'm using AxKit::XSP::IfParam along with > > > > > AxKit::XSP::AttrParam in the body to test for submission and output > > > > > the matching rows. The problem is that once I post the first time, > > > > > that's it. This persists when I leave the page and come back, but I > > > > > haven't tested it methodically enough to determine an actual pattern. > > > > > > > > > > I'm not using any session handling AxKit libraries. > > > > > I'm not getting any errors with AxLogLevel at 10. > > > > > All is from CVS, 3 days old. > > > > > > > > > > Has anyone else experienced this? > > > > > > > > > > -- Ryan > > > > > > > > > > <?xml version="1.0"?> > > > > > <?xml-stylesheet href="." type="application/x-xsp"?> > > > > > <?xml-stylesheet href="/stylesheets/general.xsl" type="text/xsl"?> > > > > > > > > Are you also using the included XSLT that comes with PerForm? > > > > Matt. > > > > > > > > > > > > --------------------------------------------------------------------- > > > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > -------------------------------------------------------------------------- - > >- ---- > > > > > --------------------------------------------------------------------- > > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
