Hi,
We have show_additional_headers 1.0 installed and activated, but due to some reason it does for instance not show the headers "Content-Type" and "Content-Transfer-Encoding". It shows "User-Agent", "Mailer", "X-Newsreader" and the like, though.
As you may have noticed, it's called "show_additional_headers", not "show_all_headers". ;-)
There is a version 1.1 available at http://trac.roundcube.net/browser/trunk/plugins/show_additional_headers?rev=... 764, can this be safely used with RC 0.7.2? And does it behave differently in this respect?
Looking at the comments at the beginning of this file, I see that an option exists to configure which headers should be shown:
Maybe you give it a try.
-Martin
Am 23.04.2012 09:15, schrieb Martin Muskulus:
We have show_additional_headers 1.0 installed and activated, but due to some reason it does for instance not show the headers "Content-Type" and "Content-Transfer-Encoding". It shows "User-Agent", "Mailer", "X-Newsreader" and the like, though.
As you may have noticed, it's called "show_additional_headers", not "show_all_headers". ;-)
Funny. As you will have noticed, it should show all headers defined in main.inc.php, right?
See your own comment below:
There is a version 1.1 available at http://trac.roundcube.net/browser/trunk/plugins/show_additional_headers?rev=..., can this be safely used with RC 0.7.2? And does it behave differently in this respect?
Looking at the comments at the beginning of this file, I see that an option exists to configure which headers should be shown:
What a surprise! :->
- Enable the plugin in config/main.inc.php and add your desired headers:
- $rcmail_config['show_additional_headers'] = array('User-Agent');
Maybe you give it a try.
If I wouldn't have given it a try already before I raised this question, a) I wouldn't have seen even ANY additional header (but which I did, as you may have read), and b) wouldn't have asked here.
The problem is that it doesn't show Content-* headers ALTHOUGH they are defined in main.inc.php. Did YOU give it a try...?
See A.L.E.C's comment before (!) your post, it's indeed an issue, but has been fixed - today. Thanks to A.L.E.C