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 349199 - Shouldn't only rely on the Content-type header when reading from HTTP.
Shouldn't only rely on the Content-type header when reading from HTTP.
Status: RESOLVED FIXED
Product: gedit
Classification: Applications
Component: general
2.15.x
Other Linux
: Normal normal
: ---
Assigned To: Gedit maintainers
Gedit maintainers
Depends on:
Blocks:
 
 
Reported: 2006-07-29 17:09 UTC by Steve Frécinaux
Modified: 2009-08-19 15:16 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Steve Frécinaux 2006-07-29 17:09:31 UTC
Not sure it belongs to gedit, but I think we shouldn't only rely on the HTTP header "Content-type" while opening a file from a remote HTTP server. This is problematic because code files are often sent as text/plain, no matter what their actual mime-type is. (and some servers interpret files being declared as python or php or perl, so sending them with right mime-type might be difficult). This causes gedit usually not to highlight the file when opened from HTTP (from a svn server or so)

For instance, try opening
https://svn.tinymail.org/svn/tinymail/trunk/libtinymail/tny-list-iface.h
and notice there is no syntax highlighting.
Comment 1 Paolo Borelli 2009-08-19 15:16:31 UTC
This now works, either because gvfs is smarted than gnome-vfs or because we fallback to using the filename... eitherway it works :)