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 779758 - gtk_show_uri() reports "HTTP error: Message Corrupt"
gtk_show_uri() reports "HTTP error: Message Corrupt"
Status: RESOLVED OBSOLETE
Product: gtk+
Classification: Platform
Component: .General
unspecified
Other Linux
: Normal normal
: ---
Assigned To: gtk-bugs
gtk-bugs
Depends on:
Blocks:
 
 
Reported: 2017-03-08 16:56 UTC by Szőgyényi Gábor
Modified: 2018-05-02 18:16 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
test.c (747 bytes, text/plain)
2017-03-10 07:23 UTC, Milan Crha
Details

Description Szőgyényi Gábor 2017-03-08 16:56:18 UTC
When I click to a link in an e-mail, a message box comes up with: "HTTP error: Message Corrupt" message. But the link works with copy-paste to the browser.
Comment 1 Milan Crha 2017-03-09 09:37:36 UTC
Thanks for a bug report. Evolution uses gtk+ function gtk_show_uri(), which in turn relies on gvfs modules/backends. Can the issue be there? I can provide you a simple C application to test this, if you can compile it.
Comment 2 Szőgyényi Gábor 2017-03-09 22:01:09 UTC
Thanks.

Yes, I can compile your simple code. But I have problem with compiling the whole evolution package. One package is missing, but nobody knows, which is missing.
Link to the compile bug: https://bugzilla.gnome.org/show_bug.cgi?id=779670
Comment 3 Milan Crha 2017-03-10 07:23:51 UTC
Created attachment 347597 [details]
test.c

Okay, good. In that case make sure you've development files for gtk3 and then save this file as test.c and compile it using the command at the comment at the top of the file. Either you can change the default URI in the code, or you can pass it from the command line, just make sure that the bash substitutions will not affect the actual URL being used.
Comment 4 Szőgyényi Gábor 2017-03-10 09:33:59 UTC
Thanks. Compiled successful. But there is no error message, the www.gnome.org homepage appears, and the clicking to URL in evolution also working.
I rebooted my comuter since than, maybe that's why the clicking is working now.

If I will run into that problem again I will check it with your test code, and I will copy-paste the error message.
Comment 5 Szőgyényi Gábor 2017-03-10 16:00:24 UTC
Hi!
The problem appeared after a few hours of computer using.
Now the "HTTP error: Message Corrupt" message comes up, when I click to a link in evolution, but your test program works perfect, without error message.
Comment 6 Szőgyényi Gábor 2017-03-10 16:06:01 UTC
Sorry, my fault.

Many links work by clicking, but this not working in evoluition: 
https://bugs.kde.org/show_bug.cgi?id=377382
Comment 7 Milan Crha 2017-03-13 09:38:21 UTC
Does this work, please?

   ./test "https://bugs.kde.org/show_bug.cgi?id=377382"

I'm wondering how the URL is encoded in the message. Could you share the message with me, please? If if contains any private information, feel free to send it only to me (as an attachment), to my bugzilla email, only name this bug report in the subject, thus I'd not overlook it in my spam folder. Thanks in advance.
Comment 8 Szőgyényi Gábor 2017-03-13 09:46:25 UTC
Your test program also gives error:


szg@debian:~$ ./test "https://bugs.kde.org/show_bug.cgi?id=377382"

** (test:5059): WARNING **: Failed to show uri 'https://bugs.kde.org/show_bug.cgi?id=377382': HTTP Error: Message Corrupt

szg@debian:~$
Comment 9 Milan Crha 2017-03-13 10:18:07 UTC
(In reply to Szőgyényi Gábor from comment #8)
> Your test program also gives error:

Good, in that case the error is in gtk+, or rather somewhere below it, like gvfs. I do not know how to recognize which part of the call stack reports this and why, thus I'm moving it to the nearest known place, gtk+.
Comment 10 GNOME Infrastructure Team 2018-05-02 18:16:13 UTC
-- GitLab Migration Automatic Message --

This bug has been migrated to GNOME's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.gnome.org/GNOME/gtk/issues/781.