Skip to content
GitLab
  • Menu
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • pike pike
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 121
    • Issues 121
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • pikelang
  • pikepike
  • Issues
  • #7653
Closed
Open
Created Feb 29, 2016 by Peter Bortas@zinoOwner

_Roxen.http_decode_string leaves surrogate pairs in resulting string

Imported from http://bugzilla.roxen.com/bugzilla/show_bug.cgi?id=7653

Reported by Martin Karlgren marty@roxen.com

_Roxen.http_decode_string claims to perform best-effort decoding of %XX and %uXXXX-encoded strings. However, surrogate pairs are passed as-is to the resulting Pike string.

Example:

> _Roxen.http_decode_string("%uD83D%uDE02");
(3) Result: "\ud83d\ude02"

Expected result: "\u1f602"

I guess an error should be thrown if an incomplete surrogate pair is encountered.

Assignee
Assign to
Time tracking