Uploaded image for project: 'Confluence Data Center'
  1. Confluence Data Center
  2. CONFSERVER-7651

Remove character encoding configuration from Confluence

XMLWordPrintable

    • We collect Confluence feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

      NOTE: This suggestion is for Confluence Server. Using Confluence Cloud? See the corresponding suggestion.

      Confluence should:

      1) Serve all pages as UTF-8
      2) Require that the application server interpret URLs as being UTF-8 encoded

      All modern browsers support this configuration, but we will have to test all our supported appservers to ensure that they can be configured to support (2). And we'll have to provide documentation on how to do this configuration on each appserver.

      This will resolve a lot of character encoding issues that are caused by users moving away from UTF-8. It will also mean we can phase out the truly ugly and bug-prone URL-rewriting and double-encoding hacks that plague the codebase.

            [CONFSERVER-7651] Remove character encoding configuration from Confluence

            Sen Geronimo made changes -
            Workflow Original: JAC Suggestion Workflow 4 [ 3572892 ] New: JAC Suggestion Workflow 3 [ 4335231 ]
            Katherine Yabut made changes -
            Workflow Original: JAC Suggestion Workflow 2 [ 3182548 ] New: JAC Suggestion Workflow 4 [ 3572892 ]
            Status Original: RESOLVED [ 5 ] New: Closed [ 6 ]
            Katherine Yabut made changes -
            Workflow Original: JAC Suggestion Workflow [ 3024644 ] New: JAC Suggestion Workflow 2 [ 3182548 ]
            Owen made changes -
            Workflow Original: Confluence Workflow - Public Facing v4 [ 2528477 ] New: JAC Suggestion Workflow [ 3024644 ]
            Rachel Lin (Inactive) made changes -
            Workflow Original: Confluence Workflow - Public Facing v3 [ 2280191 ] New: Confluence Workflow - Public Facing v4 [ 2528477 ]
            Katherine Yabut made changes -
            Workflow Original: Confluence Workflow - Public Facing v3 - TEMP [ 2164923 ] New: Confluence Workflow - Public Facing v3 [ 2280191 ]
            Katherine Yabut made changes -
            Workflow Original: Confluence Workflow - Public Facing v3 [ 1921269 ] New: Confluence Workflow - Public Facing v3 - TEMP [ 2164923 ]
            Katherine Yabut made changes -
            Workflow Original: Confluence Workflow - Public Facing v2 [ 1753638 ] New: Confluence Workflow - Public Facing v3 [ 1921269 ]
            jonah (Inactive) made changes -
            Description Original: Confluence should:

            1) Serve all pages as UTF-8
            2) Require that the application server interpret URLs as being UTF-8 encoded

            All modern browsers support this configuration, but we will have to test all our supported appservers to ensure that they can be configured to support (2). And we'll have to provide documentation on how to do this configuration on each appserver.

            This will resolve a _lot_ of character encoding issues that are caused by users moving away from UTF-8. It will also mean we can phase out the truly ugly and bug-prone URL-rewriting and double-encoding hacks that plague the codebase.             		New: {panel:bgColor=#e7f4fa}
              *NOTE:* This suggestion is for *Confluence Server*. Using *Confluence Cloud*? [See the corresponding suggestion|http://jira.atlassian.com/browse/CONFCLOUD-7651].
              {panel}

            Confluence should:

            1) Serve all pages as UTF-8
            2) Require that the application server interpret URLs as being UTF-8 encoded

            All modern browsers support this configuration, but we will have to test all our supported appservers to ensure that they can be configured to support (2). And we'll have to provide documentation on how to do this configuration on each appserver.

            This will resolve a _lot_ of character encoding issues that are caused by users moving away from UTF-8. It will also mean we can phase out the truly ugly and bug-prone URL-rewriting and double-encoding hacks that plague the codebase.
            jonah (Inactive) made changes -
            Link New: This issue relates to CONFCLOUD-7651 [ CONFCLOUD-7651 ]

              Unassigned Unassigned
              cmiller@atlassian.com Charles Miller (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: