Closed
Bug 218836
Opened 22 years ago
Closed 20 years ago
java objects not re-downloaded from server when changed
Categories
(Core Graveyard :: Java-Implemented Plugins, defect)
Tracking
(Not tracked)
RESOLVED
EXPIRED
People
(Reporter: jonplease, Assigned: blackconnect)
Details
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4) Gecko/20030701
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4) Gecko/20030701
When:
1. a java object is embedded in a webpage
2. that webpage is reloaded
3. the object has changed since the last reload
4. cache settings indicate that the user wants mozilla to check things every
time you visit a page, or when the page is out of date
Then:
Mozilla should check if the object is out of date and re-download it if necessary.
Right now I look at my server logs and see it requesting the webpage properly,
but it only gets the java object once per session, even when it's changed on disk.
Reproducible: Always
Steps to Reproduce:
0. Set cache behavior to either "every time" or "when out of date".
1. Make a really simple java applet that, say, prints a line of text in blue.
2. Make a webpage with that applet embedded.
3. View the webpage in the browser.
4. Change the applet to print in red.
5. Reload the webpage (without exiting the browser in the meantime).
Actual Results:
The applet was not reloaded.
Expected Results:
It should have reloaded the applet.
The webserver returns the Date and Last-Modified headers correctly for the java
class file. Also, mozilla behaves correctly for images, e.g. when an image
changes on disk, it is re-downloaded.
Comment 1•20 years ago
|
||
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/
Comment 2•20 years ago
|
||
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: 20 years ago
Resolution: --- → EXPIRED
Updated•14 years ago
|
Product: Core → Core Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•