Ticket #1484624 (closed Bugs: fixed)

Opened 14 months ago

Last modified 8 months ago

source view is not type text/plain -> html interpreted

Reported by: bcevc Owned by:
Priority: 5 Milestone: 0.2-alpha
Component: Client Scripts Version: 0.1-rc1
Severity: normal Keywords:
Cc: baltasar.cevc+rcd@…

Description

When opening a message then choosing source view in the current RC version, the popup window will not show the source as text/plain, but interpret it (differently in different browsers). Maybe adding a "Content-type: text/plain"-header would help?

This is particularly nasty with spam mails containing webbugs as they are loaded then.

Change History

follow-up: ↓ 2   Changed 14 months ago by thomasb

  • status changed from new to closed
  • resolution set to worksforme

"Content-type: text/plain" is correctly set.

in reply to: ↑ 1   Changed 8 months ago by trd79

  • status changed from closed to reopened
  • resolution deleted

I am having the same problem here. Latest version 0.1.1. have checked the source (viewsource.inc) and the header is correctly being set there, however it must not be taking effect (or being overridden) as the header sent to the browser is text/html.

  Changed 8 months ago by alec

  • status changed from reopened to closed
  • resolution set to worksforme
  • milestone set to 0.1.2

works for me also, check default_mimetype in php.ini

  Changed 8 months ago by trd79

  • status changed from closed to reopened
  • resolution deleted

default mimetype in php.ini is set to text/html (as it should be).

Have found the problem...

Following was in error log:

PHP Warning: Cannot modify header information - headers already sent by (output started at /var/www/mail/config/db.inc.php:70) in /var/www/mail/program/steps/mail/viewsource.inc on line 28

Checked db.inc.php:70 which was the end of the file. Removed three empty lines and some whitespace from the end of this file. Everything works ok now.

Am re-opening the ticket as this does have the potential to cause problems. Not sure of the solution though - might it be possible to use ob_start() and ob_end_flush()? Alternatively could just stick something in the wiki under known issues?

  Changed 8 months ago by alec

  • status changed from reopened to closed
  • resolution set to fixed

Now it's clear and confirmed. Fixed in r1274

Note: See TracTickets for help on using tickets.