Closed Bug 281514 Opened 20 years ago Closed 19 years ago

Reload from Server Side app pulls page from Cache instead of Server

Categories

(Firefox :: General, defect)

x86
Windows XP
defect
Not set
normal

Tracking

()

RESOLVED EXPIRED

People

(Reporter: wseubert, Assigned: bugzilla)

References

Details

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.5) Gecko/20041107 Firefox/1.0
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.5) Gecko/20041107 Firefox/1.0

I have developed a web app with JSP utilizing Tomcat. I believe I have come
accross a caching issue.

The main purpose of this site is to ask a series of questions to the user.

Servlet A: Selects a question from a Vector contain all of the remaining
questions and then forwards via the RequestDispatcher to JSP B.
JSP B: Displays the question in a HTML Form with the action of the Form going to
Servlet B.
Servlet B: Verifies the completeness of the response. Writes to the dBase.
Removes the question from the Vector that contains all of the questions. Upon
completion it redirects back to Servlet A via response.redirect(XXX) which tells
the browser to request the site XXX and this is repeated until all of the
questions have been answered.

The second time to Servlet A, I get the same question that I had the first time
and everything in Servlet B was successful. When I refresh, I get the new question.

If I change the response.redirect() to forward via the RequestDispatcher
everything works fine but I don't believe I should have to do this.

This problem doesn't happen when I run Tomcat on my development machine and
browse localy with FireFox. It only happens when I test via another PC on our
intranet.

This problem doesn't happen with IE either. 

Reproducible: Always

Steps to Reproduce:
Servlet A: Selects a question from a Vector contain all of the remaining
questions and then forwards via the RequestDispatcher to JSP B.
JSP B: Displays the question in a HTML Form with the action of the Form going to
Servlet B.
Servlet B: Verifies the completeness of the response. Writes to the dBase.
Removes the question from the Vector that contains all of the questions. Upon
completion it redirects back to Servlet A via response.redirect(XXX) which tells
the browser to request the site XXX and this is repeated until all of the
questions have been answered.

The second time to Servlet A, I get the same question that I had the first time
and everything in Servlet B was successful. When I refresh, I get the new question. 

Actual Results:  
The second time to Servlet A, I get the same question that I had the first time
and everything in Servlet B was successful. When I refresh, I get the new question. 

Expected Results:  
Reloaded Servlet A with would have giving the JSP B the correct data to display.

This problem doesn't happen when I run Tomcat on my development machine and
browse localy with FireFox. It only happens when I test via another PC on our
intranet.

This problem doesn't happen with IE either.
If you need/would like the .war file to help confirm/test this, just let me know.
*** Bug 289977 has been marked as a duplicate of this bug. ***
This is an automated message, with ID "auto-resolve01".

This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.

While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.

If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.

The latest beta releases can be obtained from:
Firefox:     http://www.mozilla.org/projects/firefox/
Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html
Seamonkey:   http://www.mozilla.org/projects/seamonkey/
This bug has been automatically resolved after a period of inactivity (see above
comment). If anyone thinks this is incorrect, they should feel free to reopen it.
Status: UNCONFIRMED → RESOLVED
Closed: 19 years ago
Resolution: --- → EXPIRED
This bug is likely not to be resolved if the relation to bug 289977 is correct. Please refer to the earlier bug 265088 which appears to be the real parent of this/these dupe(s).
You need to log in before you can comment on or make changes to this bug.