Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • G gitlabhq1
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 21
    • Issues 21
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 12
    • Merge requests 12
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Package Registry
    • Infrastructure Registry
  • Analytics
    • Analytics
    • CI/CD
    • Repository
    • Value stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • gpt
  • large_projects
  • gitlabhq1
  • Issues
  • #4023

Closed
Open
Created May 22, 2013 by Administrator@rootOwner

Regression on raw/blob content via api

Created by: dblessing

There is a nasty 5.1 to 5.2 snippets API regression when getting raw content.

In 5.1, content was output exactly as described - raw. No encoding or escaping of text whatsoever. In 5.2, content is encoded and instead of actual white space you see new line characters. You can see this in the screenshots below. The content of the screenshots is the exact same snippet, first with 5.1 and second with 5.2.

This will break any API integration tool that gets raw snippet content.

5 1snippetcontent

5 2snippetcontent

Assignee
Assign to
Time tracking