Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add support for TLS responses in v2.2.0 #140

Merged
merged 1 commit into from
Sep 4, 2019

Conversation

peschuster
Copy link
Contributor

  • What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)
    Feature / support for CasparCG v2.2

  • What is the current behavior? (You can also link to an open issue here)
    Response from CasparCG server v2.2 of TLS command is not recognized (see issue null response from tls command #112).

  • What is the new behavior (if this is a feature change)?
    Plain lists without any additional fields are assumed to be responses from CasparCG v2.2 with just the name of the template.

  • Other information
    Tested with official CasparCG release "2018-12-29 - Version 2.2.0 Stable" and used in production at two multi day events during the last months with CasparCG as video playout server and generator for lower thirds.

@mint-dewit mint-dewit changed the base branch from master to develop September 2, 2019 10:08
@mint-dewit
Copy link
Contributor

Hi and thanks for this PR. Looks like our git flow got messed up somewhere when several PR's were merged onto the master branch directly instead of develop. Could you rebase this PR and #141 on the current develop branch? Sorry for the inconvenience.

@peschuster peschuster force-pushed the feature-casparv22-tls branch from a095e33 to db03fda Compare September 2, 2019 18:10
@peschuster
Copy link
Contributor Author

No problem. I just rebased both PRs.

@mint-dewit
Copy link
Contributor

Perfect, thanks!

@mint-dewit mint-dewit merged commit 9409850 into SuperFlyTV:develop Sep 4, 2019
@peschuster peschuster deleted the feature-casparv22-tls branch September 4, 2019 15:50
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.

2 participants