Issue 74114 - Hyperlink causes writer to hang on save
Summary: Hyperlink causes writer to hang on save
Status: CLOSED WONT_FIX
Alias: None
Product: Writer
Classification: Application
Component: save-export (show other issues)
Version: OOo 2.1
Hardware: All Windows XP
: P3 Trivial (vote)
Target Milestone: ---
Assignee: Mathias_Bauer
QA Contact: issues@sw
URL:
Keywords: oooqa
Depends on:
Blocks:
 
Reported: 2007-02-02 09:19 UTC by khbellgardt
Modified: 2013-08-07 14:38 UTC (History)
1 user (show)

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


Attachments
Document including a links that timeouts (8.13 KB, application/vnd.sun.xml.writer)
2007-02-02 12:53 UTC, khbellgardt
no flags Details

Note You need to log in before you can comment on or make changes to this issue.
Description khbellgardt 2007-02-02 09:19:31 UTC
Consider a document containing a hyperlink to an external target that exists but
is not accessible (eg. because access is blocked by a firewall). When saving
this documentm writer seems to hang. Obviously during save writer tries to
access the target and then runs into a timeout of network functions that may
last several tens of seconds per hyperlink and the user gets the impression that
writer hangs.

What is this behaviour good for? I think it is completely unneccessary that
writer  accesses or checks hyperlinks when saving the document. 

The details of the reported case were as follows:

The original document was a Word-document containing hyperlinks such as
"\\computername.domain\path\" to computers in a windows network. Some time ago
this document was opened in writer and saved as sxw. Now I can no longer tell
which version of writer was used for this conversion, but at the beginning there
were no problems when saving the sxw file. Recently the document was edited and
then writer (OOo1.5 and OOo2.1) always hang during save. It was found that the
hyperlinks causing the problem where converted by writer to
"file://computername.domain/path/".
Comment 1 khbellgardt 2007-02-02 09:29:24 UTC
I said: "at the beginning there were no problems when saving the sxw file". The
reason might simply be that at that time the resource was still accessible via
the network and the firewall was established only afterwards.
Comment 2 michael.ruess 2007-02-02 10:58:32 UTC
This problem is known, see issue 28625.

*** This issue has been marked as a duplicate of 28625 ***
Comment 3 michael.ruess 2007-02-02 11:00:47 UTC
Closing duplicate.
Comment 4 Mathias_Bauer 2007-02-02 12:15:12 UTC
This is not a duplicate to issue 28625 as we can't apply the same fix to both
problems. Wether we can fix this one at all must be judged by studying a document.
Comment 5 khbellgardt 2007-02-02 12:53:59 UTC
Created attachment 42667 [details]
Document including a links that timeouts
Comment 6 khbellgardt 2007-02-02 12:57:00 UTC
I have added a document that causes a timeout during save when I am in the
domain tci.uni-hannover.de. I don't know whether it behaves same in a different
environment.
Comment 7 kpalagin 2007-02-02 19:30:10 UTC
khbellgardt,
can't repro with your doc (OO 2.1 on WinXP). Please try it yourself on some 
other machine.
Comment 8 michael.ruess 2007-02-06 14:17:34 UTC
Reassigned to ES.
Comment 9 eric.savary 2007-02-06 15:05:16 UTC
ES->MBA: as stated in your comments, please have a look.
Comment 10 Mathias_Bauer 2007-02-14 14:40:37 UTC
The reason for the hanging is that the hyperlink URL is made relative (in memory
URLs in OOo are always absolute; changing this would be a huge effort). Making a
URL relative in a platform independent way needs to care for case sensitivity
problems. So we must check every hierarchical part of the URL to check whether
it is a case sensitive or a case insensitive file system, at least we must check
the root host system. In case of an unreachable host we fail already in the
first part of the URL but at least we must try.

So I'm afraid that we don't have a fix for the problem with a justifiable effort. 
Comment 11 ace_dent 2008-05-17 21:35:46 UTC
The Issue you raised has been marked as 'Resolved' and not updated within the
last 1 year+. I am therefore setting this issue to 'Verified' as the first step
towards Closing it. If you feel this is incorrect, please re-open the issue and
add any comments.

Many thanks,
Andrew
 
Cleaning-up and Closing old Issues
~ The Grand Bug Squash, pre v3 ~
http://marketing.openoffice.org/3.0/announcementbeta.html
Comment 12 ace_dent 2008-05-17 23:39:02 UTC
As per previous posting: Verified -> Closed.
A Closed Issue is a Happy Issue (TM).

Regards,
Andrew
Comment 13 Mathias_Bauer 2009-05-07 14:32:10 UTC
I just wanted to add that I was wrong by thinking that we can't fix that without
reasonable effort. So I'm happy to tell that this issue will be fixed in OOo3.2.
Please see issue 50983.