Skip to content

fix: handle correctly semicolon on the end of the fmtp line#23

Merged
k-wasniowski merged 2 commits intomainfrom
fix-fmtp-line-should-allow-semicolon-on-end
Mar 20, 2025
Merged

fix: handle correctly semicolon on the end of the fmtp line#23
k-wasniowski merged 2 commits intomainfrom
fix-fmtp-line-should-allow-semicolon-on-end

Conversation

@k-wasniowski
Copy link
Contributor

No description provided.

@bbaldino
Copy link
Collaborator

Just to add a bit of research that we did:

Based on some links (here and here) and the spec which defines the grammar as:

a=fmtp:<dynamic payload type> <parameter
       name>=<value>[,<value>][; <parameter name>=<value>]

it appears that trailing semicolons should not technically be considered valid, but they do happen so it seems reasonable to not choke on them.

Copy link
Collaborator

@bbaldino bbaldino left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

code looks good...just tweak that comment a bit if you can

@k-wasniowski k-wasniowski merged commit f0ce5c4 into main Mar 20, 2025
1 check passed
@k-wasniowski k-wasniowski deleted the fix-fmtp-line-should-allow-semicolon-on-end branch March 20, 2025 12:29
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants