Bug 76743 - Bugzilla doesn't specify character set
Summary: Bugzilla doesn't specify character set
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Bugzilla
Classification: Community
Component: Bugzilla General (Show other bugs)
(Show other bugs)
Version: 2.18
Hardware: All Linux
medium
medium vote
Target Milestone: ---
Assignee: PnT DevOps Devs
QA Contact: David Lawrence
URL:
Whiteboard:
Keywords:
Depends On:
Blocks: 70443
TreeView+ depends on / blocked
 
Reported: 2002-10-25 17:40 UTC by Christian Rose
Modified: 2013-06-24 03:07 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2008-08-28 20:30:35 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description Christian Rose 2002-10-25 17:40:40 UTC 
Bugzilla doesn't specify what character set is used in the html output.
By default, no character set specified implies iso-8859-1, but it is good
practice to also explicitly specify this information. Also, specifying the
character set is needed for Bugzilla to support UTF-8 as mentioned in bug 70443.
Comment 1 Aleksey Nogin 2006-04-08 18:59:49 UTC 
As of 2.18, Bugzilla does specify the charset (UTF-8) in Bugzilla emails and
through the meta tag in HTML, but the HTTP header contains an empty one. Not
sure if we care about the HTTP header.

% lynx -mime_header 'https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=76743'
| head -20
HTTP/1.1 200 OK
Date: Sat, 08 Apr 2006 18:58:48 GMT
Server: Apache/2.0.46 (Red Hat)
Connection: close
Content-Type: text/html; charset=

<!-- 1.0@bugzilla.org -->








<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
  <head>
    <meta http-equiv="content-type" content="text/html; charset=UTF-8">
    <title>Bug 76743 - Bugzilla doesn't specify character set</title>
Comment 2 David Lawrence 2008-08-28 20:30:35 UTC 
This is properly fixed in recent versions of Bugzilla.
Note You need to log in before you can comment on or make changes to this bug.