Issue 54 - different content in / and index.html
Summary: different content in / and index.html
Status: CLOSED WONT_FIX
Alias: None
Product: Infrastructure
Classification: Infrastructure
Component: Mailing lists (show other issues)
Version: current
Hardware: All All
: P4 Trivial (vote)
Target Milestone: ---
Assignee: Unknown
QA Contact: issues@www
URL: http://xml.openoffice.org/xml-dev/
Keywords:
: 53 (view as issue list)
Depends on:
Blocks: 53
  Show dependency tree
 
Reported: 2000-10-25 15:22 UTC by bernd.eilers
Modified: 2012-03-01 22:52 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Latest Confirmation in: ---
Developer Difficulty: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this issue.
Description bernd.eilers 2000-10-25 15:22:31 UTC 
Content shown in mailing list entered from the project home page doesn't match 
the content shown after switching to threaded index mode and than to date index 
mode.

I've mostly recognized this behaviour for the xml-dev mailing list, but it's 
more likely a general problem.

The Link on the XML Project Home page referrs to 
http://xml.openoffice.org/xml-dev/ after toggeling modes the url shown is 
http://xml.openoffice.org/xml-dev/index.html the later often shows more up to 
date content. That is after toggeling modes you often see a new article appear 
that was not shown on entering the mailing list.
Comment 1 Unknown 2000-10-25 18:23:17 UTC 
The page you are viewing is cached in a proxy server in front of
the openoffice machine.  This cache was reloaded with the fresh content every
6 hours.....but we changed the proxy to 'refresh' every hour.  So you can
either wait an hour for the new content to be propogated to the proxy
or you can see the new content immediately by viewing the page then
clicking your left shit button and the reload button to force the caching 
proxy server to get the new fresh content.

The proxy server was put in place to be able to handle more hits per
minute on the website.
Comment 2 Unknown 2000-10-25 19:56:38 UTC 
*** Issue 53 has been marked as a duplicate of this issue. ***
Comment 3 bernd.eilers 2000-10-26 08:44:26 UTC 
If the handling is as described HTTP Expire and/or Cache-Control max-age header 
fields should show this 1 hour, but non of them are set.
See RFC2616 for details on those header fields.

You can easily check that they are missing by using telnet.
telnet xml.openoffice.org 80
GET /xml-dev/ HTTP/1.1
Host: xml.openoffice.org
Comment 4 Unknown 2000-12-11 22:52:43 UTC 
as far as i can tell, this is really a duplicate of issues being discussed
in #98.


*** This issue has been marked as a duplicate of 98 ***
Comment 5 Unknown 2000-12-11 22:55:03 UTC 
dependency on 98
Comment 6 michael.bemmer 2003-03-11 17:22:53 UTC 
As mentioned on the qa dev list on March 5th I will close all resolved duplicate
issues. Please see this posting for details. First step in IssueZilla is
unfortunately to set them to verified.
Comment 7 michael.bemmer 2003-03-11 18:01:54 UTC 
As mentioned on the qa dev list on March 5th I will close all resolved duplicate
issues. Please see this posting for details.
Comment 8 michael.bemmer 2003-03-11 18:02:05 UTC 
As mentioned on the qa dev list on March 5th I will close all resolved duplicate
issues. Please see this posting for details.
Comment 9 Rob Weir 2012-03-01 22:52:11 UTC 
Was marked as duplicate of bug #98, but 98 doesn't exist in this BZ instance.  I'm resetting this to WONTFIX in order to fix the sanity check error.