Skip to content

Fix: parsing ambiguity in cib_ops_path format handling#315

Open
aleksei-burlakov wants to merge 1 commit into
ClusterLabs:masterfrom
aleksei-burlakov:fix-resource-recent-events2
Open

Fix: parsing ambiguity in cib_ops_path format handling#315
aleksei-burlakov wants to merge 1 commit into
ClusterLabs:masterfrom
aleksei-burlakov:fix-resource-recent-events2

Conversation

@aleksei-burlakov
Copy link
Copy Markdown
Contributor

The CibController#ops action expects the :id parameter in the form ,. When Rails appends .json to the URL, resource or node names containing dots become ambiguous and require special route constraints.

The CibController#ops function expects and :id in the form , but there comes a concatenation of 3 values ,. Commit 32c1471 enables correct parsing 3 values, but it breaks the parsing in other controllers, when there is no given. One could possibly distinguish the regular expressions for each of the cases, but let's better not glue too many values together, and just move the :format out, as a separate argument.

The CibController#ops action expects the :id parameter in the
form <resource>,<node>. When Rails appends .json to the URL,
resource or node names containing dots become ambiguous and require
special route constraints.

The CibController#ops function expects and :id in the form <resource>,<node>
but there comes a concatenation of 3 values <resource>,<node><format>.
Commit 32c1471 enables correct parsing 3 values, but it breaks the parsing
in other controllers, when there is no <format> given. One could possibly
distinguish the regular expressions for each of the cases, but let's
better not glue too many values together, and just move the :format out,
as a separate argument.
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.

1 participant