Skip to content

GitLab

  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • O otrv4
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 1
    • Issues 1
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • Deployments
    • Deployments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • Value stream
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • OTRv4
  • otrv4
  • Issues
  • #137

Closed
Open
Created Apr 22, 2018 by Jurre van Bergen@DrWhaxOwner

Make default encoding explicit for (technical) string to byte-array conversions

Created by: cobratbq

There are a number of locations where we expect to convert a textual string to a byte-array. My primary use case I bumped into right now is in section Shared Session State. Here we discuss infrastructure IDs, which may very well contain unicode characters if related to modern domains.

Would it make sense to make it explicit that in such string conversion cases? Such as the infrastructure contact IDs, we assume UTF-8 encoding.

Right now there is a single occurrence where string encoding is mentioned: section Data Messages. However this reference is quite specific on it being about the payload of the data message's plain text message part.

Assignee
Assign to
Time tracking