After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 676627 - Wrong 'Type' shown in Nautilus on webdav volume
Wrong 'Type' shown in Nautilus on webdav volume
Status: RESOLVED FIXED
Product: gvfs
Classification: Core
Component: webdav backend
1.10.x
Other Linux
: Normal normal
: ---
Assigned To: gvfs-maint
gvfs-maint
Depends on:
Blocks:
 
 
Reported: 2012-05-23 10:06 UTC by Reinout van Schouwen
Modified: 2014-08-29 20:04 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
dav: Ignore parameters of the content type header (1.27 KB, patch)
2014-08-25 20:21 UTC, Ross Lagerwall 		committed Details | Review

Description Reinout van Schouwen 2012-05-23 10:06:02 UTC 
On a mounted webdav folder I have plain text files that are shown as being of "type text/plain; charset=us-ascii" in Nautilus.

Double clicking such a text file opens the 'no application to open this type of file' dialog.

Instead, the file should be recognized as a text file and opened with gedit.
Comment 1 Ross Lagerwall 2013-12-09 05:57:33 UTC 
Can you give details about the server used? I cannot reproduce this against an Apache webdav server.

If possible, rerun gvfs in debug mode [1] and then give the debug output that is shown when trying to access the file in Nautilus.

Also, please give the output of: gvfs-info dav://host/path/to/textfile.txt


[1] In Terminal: GVFS_DEBUG=all GVFS_HTTP_DEBUG=all /usr/libexec/gvfsd -r
Comment 2 André Klapper 2014-08-25 18:31:20 UTC 
Closing this bug report as no further information has been provided. Please feel free to reopen this bug if you can provide the information asked for.
Thanks!
Comment 3 Ross Lagerwall 2014-08-25 20:21:15 UTC 
Created attachment 284450 [details] [review]
dav: Ignore parameters of the content type header

Ignore parameters of the file's content type since these break
applications which make use of the content type.

E.g. If the server returns a type such as "text/plain; charset=utf-8",
the file won't open in a text editor.
Comment 4 Ross Lagerwall 2014-08-25 20:22:45 UTC 
I reproduced this with a lighttpd webdav server with a custom config. The attached patch fixes the problem.
Comment 5 Ondrej Holy 2014-08-29 09:52:09 UTC 
Review of attachment 284450 [details] [review]:

Looks good, thanks, but please add a comment why we doing it...
Comment 6 Ross Lagerwall 2014-08-29 20:04:08 UTC 
Pushed to master as 554f208e7dc065889358d05d8199a2271756b05e (with a comment). Thanks for the review!