Apache OpenOffice (AOO) Bugzilla – Issue 930
problem accessing xml spec on OO.org site
Last modified: 2003-12-06 14:52:34 UTC
If you do a search for the xml documentation one of the hits is the above (I assume defunct) page. But the page looks current. If I click on the XML File Format Specification (PDF). link, I actually load an html page. If I navigate main page-> projects -> xml then I can successfully get the xml pdf file.
I am able to duplicate this problem ... http://xml.openoffice.org/project/xml/index.html > http://xml.openoffice.org/project/xml/xml_specification_draft.pdf > vs http://xml.openoffice.org/ > http://xml.openoffice.org/xml_specification_draft.pdf However, as this relates to the XML product (project), reassigning to the corresponding owner for confirmation. If confirmed to be an OpenOffice.org infrastructure issue (rather than a project administration issue), then please reassign to openoffice-admin@collab.net (which I am adding to the CC:).
Daniel, can you have a look at this.
1) Jeff's observation is correct. 2) I can't see where the project administration did anything wrong, hence I assume it's an OOo infrastructure thing. And now for the details: The URLs http://www.openoffice.org/project/xml/, http://xml.openoffice.org/project/xml/, and http://xml.openoffice.org/ seem to get their contents from the CVS /xml/www tree. This tree contains an index.html and an xml_specification_draft.pdf, with the former containing a relative link to the latter (i.e., href="xml_spec..._draft.pdf"). For some reason, the xml_spec..._draft.pdf file gets properly displayed only when accessed through http://xml.openoffice.org/, but not through http://*.openoffice.org/project/xml/. I expected http://xml.openoffice.org/ to be an alias for http://www.openoffice.org/project/xml/, so I am quite surprised to see the xml_spec..._draft.pdf is treated differently depending on how it is accessed. Whether this is a bug or not depends those URLs are intended as aliases, or whether they have different purposes. One problem is probably that the search should have returned a http://xml.openoffice.org/ instead of an http://www.openoffice.org/project/xml/ URL. A possible work-around might be to only use absolute URLs in links, i.e. having the xml/www/index.html link to "http://xml.openoffice.org/..." instead of just using relative links. That doesn't seem proper, though. Questions to openoffice-admin@collab.net: 1) Should relative URLs be used in the HTML source? 2) What is the purpose of http://xml.openoffice.org/ vs http://www.openoffice.org/projects/xml/ ? Which files get treated differently, which ones don't? 3) The main site points to xml.openoffice.org, so I assume that is the 'main' site. Can the search be reconfigured such that it only indexes URLs frpm xml.openoffice.org, and doesn't index any project/xml/ URLs?
As this relates to the project level infrastructure, reassigning to goolie for ownership (to coordinate technical support as required toward resolution). Please Accept Issue and follow-up as required toward answering these questions.
... Changing Product: from: xml to: www BTW ... which is one reason why we didn't respond sooner.
for what it is worth, there are other instances where something like this occurs. (see http://api.openoffice.org/5.2 and http://www.openoffice.org/project/api/5.2) These have to do with the vhosting, I think. Question: will Scast resolve this issue? Or should we use absolute links? -louis
I would like to escalate this to Kat, since i believe an ops or instantiations engineer is going to have to look into this. Kat, I'm re-assigning to you for ultimate re-assignment to a technical resource. I know there is one other example of this problem as well; I'll be assigning that issues to you as well.
adding myself as cc, so I can track issue.
accepting for resouce coordination
I just spoke with an engineer about this issue. With regard to the upgrade and the links issue Louis mentioned, the directory structure is be different in SC and these changes should alleviate some of the problems you are seeing. . Issue pcn4568 has been entered internally for details and updates which I will communicate here. Thank you Kat
Relative urls of the form (for example) /xml_specification_draft.pdf should work fine in HTML source. I am researching the possibility of indexing only 'main' pages in the search. Thank you Kat
Hi, Marking as fixed based on the last upgrade. The internal issue is closed. Thank you Kat
As agreed by Louis I will close these resolved fixed kat (support)-owned issues now. If you have trouble with that, please re-open the issue.