Track name with < or > symbols causes API to return blank name

[mgoodfellow]

Title: Track name with < or > symbols causes API to return blank name

Issue found of: October 5th, 2022

Endpoint(s):

• GET https://api.soundcloud.com/tracks/1356911167

Scope(s):

• Authenticated

Issue

For track in question:

From the v2 API (captured from dev console):

However, from the API request above:

    "kind": "track",
    "id": 1356911167,
    "created_at": "2022/10/05 01:36:14 +0000",
    "duration": 184424,
    "commentable": true,
    "comment_count": 0,
    "sharing": "public",
    "tag_list": " ",
    "streamable": true,
    "embeddable_by": "all",
    "purchase_url": null,
    "purchase_title": null,
    "genre": "Hip-hop & Rap",
    "title": "",
    "description": "",
    "label_name": null,
    "release": null,
    "key_signature": null,
    "isrc": null,
    "bpm": null,
    "release_year": null,
    "release_month": null,
    "release_day": null,
    "license": "all-rights-reserved",
    "uri": "https://api.soundcloud.com/tracks/1356911167",
    "user": ...,
    "permalink_url": "https://soundcloud.com/lazy_a-y-e-rpm-allday/stay-strapped",
    "artwork_url": "https://i1.sndcdn.com/artworks-pdZ8ZjFmcoay4idx-mKjxjg-large.jpg",
    "stream_url": "https://api.soundcloud.com/tracks/1356911167/stream",
    "download_url": null,
    "waveform_url": "https://wave.sndcdn.com/PkxSdtPr7itx_m.png",
    "available_country_codes": null,
    "secret_uri": null,
    "user_favorite": false,
    "user_playback_count": 1,
    "playback_count": 7,
    "download_count": 0,
    "favoritings_count": 1,
    "reposts_count": 0,
    "downloadable": false,
    "access": "playable",
    "policy": null,
    "monetization_model": null
}

Note that "title" is blank

[mgoodfellow]

Hi @dpreussler

I saw you closed #381 with a change to the track API schema which is brilliant, thank you.

This issue from a while ago still comes up every so often related to having special characters in the track name. Any chance this could be looked at again just in case there is a simple fix that could be implemented to resolve it?

Many thanks,

Mike

[dpreussler]

this is due to some sanitizing to prevent untrusted html getting into free input fields. So it treats this one as unknown HTML tag that is getting removed
Let me discuss with the teams if there is a better way to handle these