Bug 81034 - CONFIGURATION: Extension update tries to lock update file
Summary: CONFIGURATION: Extension update tries to lock update file
Status: NEEDINFO
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version: 4.2.5.2 release
Hardware: Other Windows (All)
: medium normal
Assignee: Not Assigned
QA Contact:
URL:
Whiteboard: BSA
Keywords:
Depends on:
Blocks:
 
Reported: 2014-07-08 08:32 UTC by Werner Donné
Modified: 2014-11-03 08:47 UTC (History)
1 user (show)

See Also:
i915 platform:
i915 features:


Attachments
Excerpt from the log that shows the LOCK request. (961 bytes, text/plain)
2014-07-08 08:32 UTC, Werner Donné
Details

Description Werner Donné 2014-07-08 08:32:58 UTC
Created attachment 102419 [details]
Excerpt from the log that shows the LOCK request.

Problem description: 

While updating extensions the user is asked to login when the ODFToEPub extension is going to be updated. This is because LibreOffice issues a WebDAV LOCK request for the extension update file, for which an anonymous user doesn't have the permission. An extension update file is read-only, so there is no reason to lock it.

This has occurred on Windows 7 and 8.1.

Steps to reproduce:
1. Install the ODFToEPub extension (http://www.pincette.biz/odftoepub/download.xhtml)
2. Do an extension update

Current behavior:

The user is requested to log in.

Expected behavior:

There should be no such request. The extension update file should be read, not locked.
              
Operating System: Windows 7
Version: 4.2.5.2 release
Comment 1 Jean-Baptiste Faure 2014-07-23 18:46:34 UTC
No such problem with other extensions, especially with extensions from https://extensions.libreoffice.org. No such problem with Grammalecte extension which is on Dicollecte website and updated from there. So I guess the problem is on the ODFToEPub extension website.

Please, could you check if you have the same problem for other extensions?
Set status to NEEDINFO. Please, set it back to UNCONFIRMED once you have provided requested informations. 

Best regards. JBF
Comment 2 Werner Donné 2014-08-02 07:00:02 UTC
I suppose the extensions.libreoffice.org simply ignores the LOCK method. You check its access log to see if it receives such requests and what the status code is it returns.
Comment 3 Werner Donné 2014-11-03 08:47:02 UTC
Imagine a LOCK request would actually be honoured by the server. Subsequent LOCK requests by other users would then fail. It would mean users can update an extension only one at the time.


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.